| NE Name: | Parvez |
| NE Type: | PCS |
| Msg Set: | all |
| Msg ID: | all |
| Detailed output: | true |
| Severity Level: | cleared |
| Including Ascending Severity Levels: | true |
| Only events with annotation: | false |
| Total Number: | 6404 |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unique constraint (%s.%s) violated |
| Long Text: | An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level. |
| Repair Text: | From Oracle doc: Either remove the unique restriction or do not insert the key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-17 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | session requested to set trace event |
| Long Text: | The current session was requested to set a trace event by another session. |
| Repair Text: | From Oracle doc: This is used internally; no action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of sessions exceeded |
| Long Text: | All session state objects are in use. |
| Repair Text: | From Oracle doc: Increase the value of the SESSIONS initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of session licenses exceeded |
| Long Text: | All licenses are in use. |
| Repair Text: | From Oracle doc: Increase the value of the LICENSE MAX SESSIONS initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-20 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of processes (%s) exceeded |
| Long Text: | All process state objects are in use. |
| Repair Text: | From Oracle doc: Increase the value of the PROCESSES initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session attached to some other process; cannot switch session |
| Long Text: | The user session is currently used by others. |
| Repair Text: | From Oracle doc: Do not switch to a session attached to some other process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid session ID; access denied |
| Long Text: | Either the session specified does not exist or the caller does not have the privilege to access it. |
| Repair Text: | From Oracle doc: Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session references process private memory; cannot detach session |
| Long Text: | An attempt was made to detach the current session when it contains references to process private memory. |
| Repair Text: | From Oracle doc: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database links and/or cursors. Detaching a session with operating system privileges is always disallowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | logins from more than one process not allowed in single-process mode |
| Long Text: | An attempt was made to log in more than once from different processes for Oracle started in single-process mode. |
| Repair Text: | From Oracle doc: Log off from the other process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to allocate %s |
| Long Text: | An application failed because Oracle ran out of memory. |
| Repair Text: | From Oracle doc: Restart Oracle with a larger SGA heap. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid session ID |
| Long Text: | The session ID string specified in the ALTER SYSTEM KILL SESSION command was invalid, or no string was specified. |
| Repair Text: | From Oracle doc: Retry the command with a valid session ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot kill current session |
| Long Text: | An attempt was made to use ALTER SYSTEM KILL SESSION to kill the current session. |
| Repair Text: | From Oracle doc: If it is necessary to kill the current session, do so from another session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | your session has been killed |
| Long Text: | A privileged user killed the session and it is no longer logged in to the database. |
| Repair Text: | From Oracle doc: Contact the database administrator. The administrator may be attempting to perform an operation that requires users to be logged out. When the database administrator announces that the database is available, log in and resume work. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session is not a user session |
| Long Text: | The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session. For example, the session may be recursively started. |
| Repair Text: | From Oracle doc: Retry the command with a valid session ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | User session ID does not exist. |
| Long Text: | The user session ID no longer exists, probably because the session was logged out. |
| Repair Text: | From Oracle doc: Use a valid session ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-31 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | session marked for kill |
| Long Text: | The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately because the session is involved in a non-interruptible operation (for example, rolling back a transaction or being blocked by a network operation). The session has been marked to be killed as soon as possible after the current operation is done. |
| Repair Text: | From Oracle doc: No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-32 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid session migration password |
| Long Text: | The session migration password specified in a session creation call was invalid (probably too long). |
| Repair Text: | From Oracle doc: Retry with a valid password (less than 30 characters). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-33 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | current session has empty migration password |
| Long Text: | An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed. |
| Repair Text: | From Oracle doc: Create the session with a non-empty migration password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-34 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot %s in current PL/SQL session |
| Long Text: | An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled by a ALTER SESSION DISABLE COMMIT IN PROCEDURE statement. |
| Repair Text: | From Oracle doc: Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-35 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LICENSE_MAX_USERS cannot be less than current number of users |
| Long Text: | Specified values for LICENSE_MAX_USERS is less than the current number of users. |
| Repair Text: | From Oracle doc: Check the license limit and drop extra users or purchase more licenses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-36 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of recursive SQL levels (%s) exceeded |
| Long Text: | An attempt was made to go more than the specified number of recursive SQL levels. |
| Repair Text: | From Oracle doc: Remove the recursive SQL, possibly a recursive trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-37 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot switch to a session belonging to a different server group |
| Long Text: | An attempt was made to switch to a session in a different server group. This is not allowed. |
| Repair Text: | From Oracle doc: Make sure the server switches to a session that belongs to its server group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-38 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot create session: server group belongs to another user |
| Long Text: | An attempt was made to create a non-migratable session in a server group that is owned by a different user. |
| Repair Text: | From Oracle doc: A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user log in in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-50 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operating system error occurred while obtaining an enqueue |
| Long Text: | Could not obtain the operating system resources necessary to cover an Oracle enqueue. This is normally the result of an operating system user quota that is too low. |
| Repair Text: | From Oracle doc: Look up the operating system error in your system documentation and perform the needed action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-51 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | timeout occurred while waiting for a resource |
| Long Text: | This message is usually caused by an instance that has terminated abnormally. |
| Repair Text: | From Oracle doc: Restart any non-recovered instances. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-52 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of enqueue resources (%s) exceeded |
| Long Text: | Ran out of enqueue resources. |
| Repair Text: | From Oracle doc: Increase the value of the ENQUEUE_RESOURCES initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-53 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of enqueues exceeded |
| Long Text: | Ran out of enqueue state objects. |
| Repair Text: | From Oracle doc: Increase the value of the ENQUEUES initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-54 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resource busy and acquire with NOWAIT specified |
| Long Text: | The NOWAIT keyword forced a return to the command prompt because a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command. |
| Repair Text: | From Oracle doc: Try the command after a few minutes or enter the command without the NOWAIT keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-55 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of DML locks exceeded |
| Long Text: | Ran out of DML lock state objects. |
| Repair Text: | From Oracle doc: Increase the value of the DML_LOCKS initialization parameter and restart Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-56 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DDL lock on object '%s.%s' is already held in an incompatible mode |
| Long Text: | The attempted lock is incompatible with the DDL lock already held on the object. This happens if you attempt to drop a table that has parse locks. |
| Repair Text: | From Oracle doc: Before attempting to drop a table, check that it has no parse locks. Wait a few minutes before retrying the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-57 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of temporary table locks exceeded |
| Long Text: | The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts. |
| Repair Text: | From Oracle doc: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and restart Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-58 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DB_BLOCK_SIZE must be %s to mount this database (not %s) |
| Long Text: | The value of the DB_BLOCK_SIZE initialization parameter used to start this database does not match the value used when that database was created. Potential reasons for this mismatch are: mounting the wrong database using the wrong initialization parameter file the value of the DB_BLOCK_SIZE parameter was changed |
| Repair Text: | From Oracle doc: For one of the above causes, either: mount the correct database use the correct initialization parameter file correct the value of the DB_BLOCK_SIZE parameter |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-59 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of DB_FILES exceeded |
| Long Text: | The value of the DB_FILES initialization parameter was exceeded. |
| Repair Text: | From Oracle doc: Increase the value of the DB_FILES parameter and restart Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-60 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | deadlock detected while waiting for resource |
| Long Text: | Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more statements were rolled back for the other session to continue work. |
| Repair Text: | From Oracle doc: Either: Enter a ROLLBACK statement and re-execute all statements since the last commit or Wait until the lock is released, possibly a few minutes, and then re-execute the rolled back statements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-61 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | another instance has a different DML_LOCKS setting |
| Long Text: | The shared instance being started is using DML locks, and the running instances are not, or vice-versa. |
| Repair Text: | From Oracle doc: Either: Do not use DML_LOCKS by setting DML_LOCKS to zero at all instances or Use DML_LOCKS by setting DML_LOCKS to a positive integer at all instances. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-62 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DML full-table lock cannot be acquired; DML_LOCKS is 0 |
| Long Text: | The instance was started with the value of DML_LOCKS set to zero, and the statement being executed needs a full-table lock (S, X, or SSX). |
| Repair Text: | From Oracle doc: Restart the instance with DML_LOCKS not equal to zero, and re-execute the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-63 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | maximum number of LOG_FILES exceeded |
| Long Text: | The value of the LOG_FILES initialization parameter was exceeded. |
| Repair Text: | From Oracle doc: Increase the value of the LOG_FILES initialization parameter and restart Oracle. The value of the parameter needs to be as large as the highest number of log files that currently exist rather than just the count of logs that exist. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-64 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object is too large to allocate on this O/S (%s,%s) |
| Long Text: | An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system. |
| Repair Text: | From Oracle doc: Reduce the value of the initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-65 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | initialization of FIXED_DATE failed |
| Long Text: | The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss. |
| Repair Text: | From Oracle doc: Make sure the initialization parameter is in the correct date format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-66 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | LOG_FILES is %s but needs to be %s to be compatible |
| Long Text: | The maximum number of log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open. |
| Repair Text: | From Oracle doc: Change the value of the LOG_FILES initialization parameter to be compatible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-67 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s for parameter %s; must be at least %s |
| Long Text: | The value for the initialization parameter is invalid. |
| Repair Text: | From Oracle doc: Choose a value as indicated by the message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-68 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s for parameter %s, must be between %s and %s |
| Long Text: | The value for the initialization parameter is invalid. |
| Repair Text: | From Oracle doc: Choose a value as indicated by the message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-69 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot acquire lock -- table locks disabled for %s |
| Long Text: | A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE... ADD (...), and so on. |
| Repair Text: | From Oracle doc: Use the ALTER TABLE... ENABLE TABLE LOCK command, and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-70 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | command %s is not valid |
| Long Text: | An invalid debugger command was specified. |
| Repair Text: | From Oracle doc: Type HELP to see the list of available commands. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-71 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | process number must be between 1 and %s |
| Long Text: | An invalid process number was specified. |
| Repair Text: | From Oracle doc: Specify a valid process number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-72 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | process "%s" is not active |
| Long Text: | An invalid process was specified. |
| Repair Text: | From Oracle doc: Specify a valid process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-73 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | command %s takes between %s and %s argument(s) |
| Long Text: | An incorrect number of arguments was specified. |
| Repair Text: | From Oracle doc: Specify the correct number of arguments. Type HELP to see the list of commands and their syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-74 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no process has been specified |
| Long Text: | No debug process has been specified. |
| Repair Text: | From Oracle doc: Specify a valid process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-75 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | process "%s" not found in this instance |
| Long Text: | The specified process was not logged on to the current instance. |
| Repair Text: | From Oracle doc: Specify a valid process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-76 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | dump %s not found |
| Long Text: | An attempt was made to invoke a dump that does not exist. |
| Repair Text: | From Oracle doc: Type DUMPLIST to see the list of available dumps. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-77 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | dump %s is not valid |
| Long Text: | An attempt was made to invoke an invalid dump. |
| Repair Text: | From Oracle doc: Try another dump. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-78 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot dump variables by name |
| Long Text: | An attempt was made to dump a variable by name on a system that does not support this feature. |
| Repair Text: | From Oracle doc: Try the PEEK command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-79 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | variable %s not found |
| Long Text: | An attempt was made to dump a variable that does not exist. |
| Repair Text: | From Oracle doc: Use a valid variable name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-80 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid global area specified by level %s |
| Long Text: | An attempt was made to dump an invalid global area. |
| Repair Text: | From Oracle doc: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use extra + level to dump global area level as well as extra bytes for every pointer; extra must be a multiple of 4. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-81 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | address range [%s, %s) is not readable |
| Long Text: | An attempt was made to read/write an invalid memory address range. |
| Repair Text: | From Oracle doc: Try another address or length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-82 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | memory size of %s is not in valid set of [1], [2], [4]stringstringstringstring%s |
| Long Text: | An invalid length was specified for the POKE command. |
| Repair Text: | From Oracle doc: Use a valid length (either 1, 2, 4, or possibly 8). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-83 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | warning: possibly corrupt SGA mapped |
| Long Text: | Even though there may be SGA corruptions, the SGA was mapped. |
| Repair Text: | From Oracle doc: Use the DUMPSGA command to dump the SGA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-84 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | global area must be PGA, SGA, or UGA |
| Long Text: | An attempt was made to dump an invalid global area. |
| Repair Text: | From Oracle doc: Specify either PGA, SGA, or UGA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-85 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | current call does not exist |
| Long Text: | An invalid attempt was made to dump the current call heap. |
| Repair Text: | From Oracle doc: Wait until the process starts a call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-86 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | user call does not exist |
| Long Text: | An invalid attempt was made to dump the user call heap. |
| Repair Text: | From Oracle doc: Wait until the process starts a call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-87 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | command cannot be executed on remote instance |
| Long Text: | An OPS command was issued for a non-OPS ORADEBUG command. |
| Repair Text: | From Oracle doc: Issue the command without the OPS syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-88 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | command cannot be executed by MTS server |
| Long Text: | A debug command was issued on an MTS server. |
| Repair Text: | From Oracle doc: Reissue the command using a dedicated server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-89 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid instance number in ORADEBUG command |
| Long Text: | An invalid instance number was specified in an OPS ORADEBUG command. |
| Repair Text: | From Oracle doc: Reissue the command with valid instance numbers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-90 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to allocate memory for OPS ORADEBUG command |
| Long Text: | Could not allocate the memory needed to execute parallel ORADEBUG. |
| Repair Text: | From Oracle doc: Reissue the command on each instance with single-instance ORADEBUG. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-91 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LARGE_POOL_SIZE must be at least %s |
| Long Text: | The value of LARGE_POOL_SIZE is below the minimum size. |
| Repair Text: | From Oracle doc: Increase the value of LARGE_POOL_SIZE past the minimum size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-92 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC |
| Long Text: | The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC. |
| Repair Text: | From Oracle doc: Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-93 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s must be between %s and %s |
| Long Text: | The parameter value is not in a valid range. |
| Repair Text: | From Oracle doc: Modify the parameter value to be within the specified range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-94 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s requires an integer value |
| Long Text: | The parameter value is not an integer. |
| Repair Text: | From Oracle doc: Modify the parameter value to be an integer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-96 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s for parameter %s, must be from among %s |
| Long Text: | The value for the initialization parameter is invalid. |
| Repair Text: | From Oracle doc: Choose a value as indicated by the message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-97 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | use of Oracle SQL feature not in SQL92 %s Level |
| Long Text: | An attempt was made to use an Oracle SQL feature that is not compliant with the SQL92 standard. |
| Repair Text: | From Oracle doc: Do not use the feature or use the ALTER SESSION SET FLAGGER command to set the appropriate level of SQL92 compliance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-99 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | timed out while waiting for resource, potential PDML deadlock |
| Long Text: | The resource needed by the transaction was busy. The PDML transaction could not acquire the resource within the specified amount of time. This indicates potential deadlock involving this PDML transaction and other transactions currently running in the system. |
| Repair Text: | From Oracle doc: Increase the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter; then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no data found |
| Long Text: | An application made a reference to unknown or inaccessible data. |
| Repair Text: | From Oracle doc: Handle this condition within the application or make appropriate modifications to the application code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid specification for system parameter MTS_DISPATCHERS |
| Long Text: | The syntax for the MTS_DISPATCHERS parameter is incorrect. |
| Repair Text: | From Oracle doc: Enter the MTS_DISPATCHERS parameter into the initialization parameter file with the correct syntax and then shut down and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | network protocol %s cannot be used by dispatchers |
| Long Text: | The network specified in MTS_DISPATCHERS does not have the functionality required by the dispatchers. |
| Repair Text: | From Oracle doc: Refer to your Oracle operating system-specific documentation for network protocols supported by the dispatchers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid network protocol; reserved for use by dispatchers |
| Long Text: | The network specified in the Net8 connect string is reserved for use by the dispatchers. |
| Repair Text: | From Oracle doc: Specify other network protocols in the connection string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-104 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | deadlock detected; all public servers blocked waiting for resources |
| Long Text: | All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources. |
| Repair Text: | From Oracle doc: Increase the limit for the system parameter MTS_MAX_SERVERS as the system will automatically start new servers to break the deadlock until the number of servers reaches the value specified in MTS_MAX_SERVERS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dispatching mechanism not configured for network protocol %s |
| Long Text: | An attempt was made to alter the dispatcher's configuration for a network protocol that was not specified in the INIT.ORA file. |
| Repair Text: | From Oracle doc: Do one of the following: Include the network protocol in the definition for the MTS_DISPATCHERS initialization parameter and restart the system. Use the ALTER SYSTEM SET MTS_DISPATCHERS command with a network protocol that exists in the initialization parameter file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-106 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | cannot startup/shutdown database when connected to a dispatcher |
| Long Text: | An attempt was made to start or shut down an instance while connected to a shared server via a dispatcher. |
| Repair Text: | From Oracle doc: Reconnect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to connect to ORACLE listener process |
| Long Text: | Most likely due to the fact that the network listener process has not been started. |
| Repair Text: | From Oracle doc: Check for the following: The network configuration file is not set up correctly. The client side address is not specified correctly. The listener initialization parameter file is not set up correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to set up dispatcher to accept connection asynchronously |
| Long Text: | The network protocol used by the dispatcher does not support asynchronous operations. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no servers started because number of servers is limited to %s |
| Long Text: | An attempt was made to start more servers than the maximum number specified by the system parameter MTS_MAX_SERVERS. |
| Repair Text: | From Oracle doc: Increase the value of the MTS_MAX_SERVERS initialization parameter as needed or re-issue the ALTER SYSTEM SET MTS_SERVERS command with an appropriate number of servers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only created up to %s (maximum specified) dispatchers |
| Long Text: | An attempt was made to start more dispatchers than the maximum number specified by the system parameter MTS_MAX_DISPATCHERS. |
| Repair Text: | From Oracle doc: Increase the value of the MTS_MAX_DISPATCHERS initialization parameter as needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-113 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | protocol name %s is too long |
| Long Text: | A protocol name specified in the MTS_DISPATCHERS initialization parameter is too long. |
| Repair Text: | From Oracle doc: Use a valid protocol name for the MTS_DISPATCHERS value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing value for system parameter MTS_SERVICE |
| Long Text: | No value was specified for the MTS_SERVICE initialization parameter, nor for the DB_NAME parameter. |
| Repair Text: | From Oracle doc: Add an MTS_SERVICE or DB_NAME definition to the initialization file. By default, MTS_SERVICE is the value of DB_NAME unless MTS_SERVICE is explicitly specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection refused; dispatcher connection table is full |
| Long Text: | A connection request was refused by a dispatcher because the dispatcher cannot support any more connections. |
| Repair Text: | From Oracle doc: Connect to a different dispatcher or use a dedicated server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-116 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | MTS_SERVICE name is too long |
| Long Text: | The service name specified in the MTS_SERVICE initialization parameter is too long. |
| Repair Text: | From Oracle doc: Use a shorter name for the MTS_SERVICE value (less than or equal to 255 characters). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-117 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value out of range for system parameter MTS_SERVERS |
| Long Text: | The specified value of the MTS_SERVERS parameter is incorrect. |
| Repair Text: | From Oracle doc: MTS_SERVERS must be greater than or equal to 0 and less than or equal to the value of MTS_MAX_SERVERS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-118 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value out of range for system parameter MTS_DISPATCHERS |
| Long Text: | The value of the MTS_DISPATCHERS parameter is incorrect. |
| Repair Text: | From Oracle doc: The sum of all MTS_DISPATCHERS values must be greater than or equal to 0 and less than or equal to the value of MTS_MAX_DISPATCHERS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-119 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid specification for system parameter MTS_LISTENER_ADDRESS |
| Long Text: | The syntax for the MTS_LISTENER_ADDRESS parameter is incorrect. |
| Repair Text: | From Oracle doc: Refer to the Oracle8i Reference manual for the correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dispatching mechanism not enabled or installed |
| Long Text: | Either the dispatching mechanism was not enabled or the Oracle executable image was not installed with the dispatching mechanism. |
| Repair Text: | From Oracle doc: Refer to the Oracle8i Administrator's Guide and your operating system-specific documentation for procedures for starting and configuration the dispatcher process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MTS_SERVERS specified without MTS_DISPATCHERS |
| Long Text: | A definition for MTS_SERVERS was specified in the INIT.ORA file, but no definition for MTS_DISPATCHERS was specified. Without a value for MTS_DISPATCHERS, shared servers will never be used. |
| Repair Text: | From Oracle doc: Add a definition for MTS_DISPATCHERS in the INIT.ORA file (or take out the definition for MTS_SERVERS, if MTS is not being used). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot initialize network configuration |
| Long Text: | Oracle could not initialize Net8. |
| Repair Text: | From Oracle doc: See accompanying messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | idle public server terminating |
| Long Text: | Too many idle servers were waiting on the common queue. |
| Repair Text: | From Oracle doc: This error is used internally, no action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MTS_DISPATCHERS specified without MTS_MAX_SERVERS |
| Long Text: | A definition for MTS_DISPATCHERS was specified in the INIT.ORA file, but MTS_MAX_SERVERS was specified as zero. |
| Repair Text: | From Oracle doc: Specify MTS_MAX_SERVERS to be greater than zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection refused; invalid presentation |
| Long Text: | The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported. |
| Repair Text: | From Oracle doc: Correct the PRESENTATION specified in the TNS address. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection refused; invalid duplicity |
| Long Text: | The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported. |
| Repair Text: | From Oracle doc: Correct the DUPLICITY specified in the TNS address. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dispatcher %s does not exist |
| Long Text: | There is currently no dispatcher running with the specified name. |
| Repair Text: | From Oracle doc: Retry with a name of the form "D###" denoting an existing dispatcher process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-128 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | this command requires a dispatcher name |
| Long Text: | Wrong syntax for ALTER SYSTEM SHUTDOWN. |
| Repair Text: | From Oracle doc: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate transaction ID |
| Long Text: | An attempt was made to start a new transaction with an ID already in use by an existing transaction. |
| Repair Text: | From Oracle doc: Check your application. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid transaction ID |
| Long Text: | The specified transaction ID does not correspond to an existing valid transaction. |
| Repair Text: | From Oracle doc: Check your application. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | current session does not match requested session |
| Long Text: | The current session is not the same as the session that was passed into a UPIXADO() call. |
| Repair Text: | From Oracle doc: Check your application. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error in XA library |
| Long Text: | The XA library could not access thread-specific pointers. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-154 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | protocol error in transaction monitor |
| Long Text: | The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended. |
| Repair Text: | From Oracle doc: Contact the transaction monitor customer support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform work outside of global transaction |
| Long Text: | The application tried to perform some work on an Oracle 7.3 server outside of a global transaction. |
| Repair Text: | From Oracle doc: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | global transaction length %s is greater than maximum (%s) |
| Long Text: | An external global transaction ID with a too large length field was passed in. |
| Repair Text: | From Oracle doc: Report the problem to your external transaction coordinator vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction branch length %s is illegal (maximum allowed %s) |
| Long Text: | An external transaction branch ID with a length either too large or 0 was passed in. |
| Repair Text: | From Oracle doc: Report the problem to your external transaction coordinator vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | external dbid length %s is greater than maximum (%s) |
| Long Text: | An external database name with too large a length field was passed in. |
| Repair Text: | From Oracle doc: Report the problem to your external transaction coordinator vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal database name length %s is greater than maximum (%s) |
| Long Text: | An internal database name with a too large length field was passed in. |
| Repair Text: | From Oracle doc: Report the problem to your external transaction coordinator vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile could not be created |
| Long Text: | It was not possible to create the control file. |
| Repair Text: | From Oracle doc: Check that there is sufficient disk space and no conflicts in file names and try to create the control file again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile version %s incompatible with ORACLE version %s |
| Long Text: | The control file was created by incompatible software. |
| Repair Text: | From Oracle doc: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-202 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | controlfile: '%s' |
| Long Text: | This message reports the name file involved in other messages. |
| Repair Text: | From Oracle doc: See associated error messages for a description of the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | using the wrong controlfiles |
| Long Text: | The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file. |
| Repair Text: | From Oracle doc: Check that the correct control files were specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in reading (block %s, # blocks %s) of controlfile |
| Long Text: | A disk I/O failure was detected on reading the control file. |
| Repair Text: | From Oracle doc: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle's inability to read the disk or control file. See the Oracle8i Administrator's Guide for information on recovering from the loss of a control file. See also your operation system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in identifying controlfile, check alert log for more info |
| Long Text: | The system could not find a control file of the specified name and size. |
| Repair Text: | From Oracle doc: One of the following: Check that the proper control file name is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again. When using mirrored control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file with a new file name in the initialization parameter file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in writing (block %s, # blocks %s) of controlfile |
| Long Text: | A disk I/O failure was detected on writing to the control file. |
| Repair Text: | From Oracle doc: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle's inability to write to the disk or control file. See the Oracle8i Administrator's Guide for information on recovering from the loss of a control file. See also your operation system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfiles are not for the same database |
| Long Text: | The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name. |
| Repair Text: | From Oracle doc: Check that the control file is for the correct database and is not an old version. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of controlfile names exceeds limit of %s |
| Long Text: | An attempt was made to use more control files than Oracle supports. |
| Repair Text: | From Oracle doc: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete unused files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | control file blocksize mismatch, check alert log for more info |
| Long Text: | The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter. |
| Repair Text: | From Oracle doc: Reduce the block size to the amount specified in the message and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot open the specified controlfile |
| Long Text: | Cannot open the control file. |
| Repair Text: | From Oracle doc: Check to make sure the control file exists and is not locked by some other program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile does not match previous controlfiles |
| Long Text: | A control file was specified that belongs to another database. |
| Repair Text: | From Oracle doc: Find and install the correct control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | block size %s below minimum required size of %s bytes |
| Long Text: | The block size specified was too small. Space for the system overhead is required. |
| Repair Text: | From Oracle doc: Specify a larger block size and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot reuse controlfile; old file size %s, %s required |
| Long Text: | To reuse a control file, it must be the same size as the one previously used. |
| Repair Text: | From Oracle doc: Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile '%s' version %s inconsistent with file '%s' version %s |
| Long Text: | An inconsistent set of control files, datafiles, and redo log files was used. |
| Repair Text: | From Oracle doc: Use a consistent set of control files, datafiles, and redo log files. That is, all the files must be for the same database and from the same time period. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must be at least one controlfile |
| Long Text: | No control file is specified or the control file specified does not exist. |
| Repair Text: | From Oracle doc: Specify at least one valid control file and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile could not be resized for migration from 8.0.2 |
| Long Text: | Control files created by release 8.0.2 were missing some records. These records are automatically added by resizing the control file when attempting to run a later release. The resize failed. |
| Repair Text: | From Oracle doc: Look in the alert log for the reason that the resize failed. If it can be fixed by giving the control file more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | block size %s of controlfile does not match DB_BLOCK_SIZE (%s) |
| Long Text: | The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database. |
| Repair Text: | From Oracle doc: Restore a good copy of the control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | required controlfile size %s exceeds maximum allowable size %s |
| Long Text: | An invocation of CREATE DATABASE, CREATE CONTROLFILE, cfileCalcSizeList, or cfileCalcSizeArray was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value. |
| Repair Text: | From Oracle doc: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses. In the case of cfileCalcSizeList() or cfileCalcSizeArray(), use a different combination of record type counts. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-220 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile not mounted by first instance, check alert log for more info |
| Long Text: | The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file. |
| Repair Text: | From Oracle doc: Find and install the correct control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-221 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error on write to controlfile |
| Long Text: | An error occurred when writing to one or more of the control files. |
| Repair Text: | From Oracle doc: See accompanying messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-222 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | operation would reuse name of a currently mounted controlfile |
| Long Text: | The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file. |
| Repair Text: | From Oracle doc: Retry the operation with a different file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-223 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | convert file is invalid or incorrect version |
| Long Text: | An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when the ALTER DATABASE CONVERT command is issued. |
| Repair Text: | From Oracle doc: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-224 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile resize attempted with illegal record type (%s) |
| Long Text: | An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter. |
| Repair Text: | From Oracle doc: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1 to 16). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-225 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | expected size %s of controlfile differs from actual size %s |
| Long Text: | The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted. |
| Repair Text: | From Oracle doc: Restore a good copy of the control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-226 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation disallowed while alternate controlfile open |
| Long Text: | The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access. |
| Repair Text: | From Oracle doc: Retry the operation after calling cfileUseCurrent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-227 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | corrupt block detected in controlfile: (block %s, # blocks %s) |
| Long Text: | A block header corruption or checksum error was detected on reading the control file. |
| Repair Text: | From Oracle doc: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-228 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | length of alternate controlfile name exceeds maximum of %s |
| Long Text: | The specified file name, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum file name length for this operating system. |
| Repair Text: | From Oracle doc: Retry the operation with a shorter file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-229 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation disallowed: already hold snapshot controlfile enqueue |
| Long Text: | The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue. |
| Repair Text: | From Oracle doc: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation disallowed: snapshot controlfile enqueue unavailable |
| Long Text: | The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue. |
| Repair Text: | From Oracle doc: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot controlfile has not been named |
| Long Text: | During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot, it was detected that no file name for the snapshot control file had previously been specified. |
| Repair Text: | From Oracle doc: Specify a name for the snapshot control file by calling cfileSetSnapshotName. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot controlfile is nonexistent, corrupt, or unreadable |
| Long Text: | The snapshot control file was found to be non-existent, corrupt, or unreadable during an invocation of cfileUseSnapshot. |
| Repair Text: | From Oracle doc: Call cfileMakeAndUseSnapshot again (or for the first time). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | copy controlfile is corrupt or unreadable |
| Long Text: | The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy. |
| Repair Text: | From Oracle doc: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same file name that was specified for cfileUseCopy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in identifying or opening snapshot or copy controlfile |
| Long Text: | A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy. |
| Repair Text: | From Oracle doc: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile fixed table inconsistent due to concurrent update |
| Long Text: | Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information. |
| Repair Text: | From Oracle doc: Retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-236 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | snapshot operation disallowed: mounted controlfile is a backup |
| Long Text: | Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file. |
| Repair Text: | From Oracle doc: Mount a current control file and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-237 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | snapshot operation disallowed: controlfile newly created |
| Long Text: | An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made. |
| Repair Text: | From Oracle doc: Mount a current control file and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-238 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | operation would reuse a filename that is part of the database |
| Long Text: | The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database. |
| Repair Text: | From Oracle doc: Retry the operation with a different file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archiver not started |
| Long Text: | An attempt was made to stop automatic archiving, but the archiver process was not running. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as %s %s |
| Long Text: | The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command. |
| Repair Text: | From Oracle doc: Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-252 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s is empty, cannot archive |
| Long Text: | A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However, it is possible that the instance died during a log switch and the log was empty. |
| Repair Text: | From Oracle doc: Empty logs do not need to be archived. Do not attempt to archive the redo log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-253 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | character limit %s exceeded by archive destination %s %s |
| Long Text: | The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long. |
| Repair Text: | From Oracle doc: Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-254 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in archive control %s '%s' |
| Long Text: | The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter. |
| Repair Text: | From Oracle doc: Check the archive string used to make sure it refers to a valid online device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-255 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error archiving log %s of thread %s, sequence # %s |
| Long Text: | An error occurred during archiving. |
| Repair Text: | From Oracle doc: Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-256 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot translate archive destination %s %s |
| Long Text: | The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated. |
| Repair Text: | From Oracle doc: Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-257 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archiver error. Connect internal only, until freed. |
| Long Text: | The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file. |
| Repair Text: | From Oracle doc: Check the archiver trace file for a detailed description of the problem. Also, verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-258 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | manual archiving in NOARCHIVELOG mode must identify log |
| Long Text: | The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or file name. |
| Repair Text: | From Oracle doc: Specify the log by file name, by group number or by thread and sequence number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-259 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of open thread %s is the current log, cannot archive |
| Long Text: | An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries. |
| Repair Text: | From Oracle doc: Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot find online log sequence %s for thread %s |
| Long Text: | The log sequence number supplied in the ARCHIVE statement does not match any of the online logs for the thread. This can result from any of the following situations: The log might have been reused for another sequence number. The log might have been dropped. The sequence number might be greater than the current log sequence number. The thread might not have any logs. |
| Repair Text: | From Oracle doc: Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-261 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | log %s of thread %s is being archived or modified |
| Long Text: | The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log. |
| Repair Text: | From Oracle doc: Wait for the current operation to complete and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | current log %s of closed thread %s cannot switch |
| Long Text: | The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused. |
| Repair Text: | From Oracle doc: Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-263 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | there are no logs that need archiving for thread %s |
| Long Text: | An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-264 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | no recovery required |
| Long Text: | An attempt was made to perform media recovery on files that do not need any type of recovery. |
| Repair Text: | From Oracle doc: Do not attempt to perform media recovery on the selected files. Check to see that the file names were entered properly. If not, retry the command with the proper file names. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | instance recovery required, cannot set ARCHIVELOG mode |
| Long Text: | The database either crashed or was shut down with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles. |
| Repair Text: | From Oracle doc: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name of archived log file needed |
| Long Text: | During media recovery, the name of an archived redo log file was requested, but no name was entered. |
| Repair Text: | From Oracle doc: Mount the correct redo log file and enter its name when it is requested. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-267 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | name of archived log file not needed |
| Long Text: | During media recovery, the name of an archived redo log file was entered, but no name was requested. |
| Repair Text: | From Oracle doc: Continue media recovery, but do not enter a new log name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-268 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified log file does not exist '%s' |
| Long Text: | The given redo log file does not exist. |
| Repair Text: | From Oracle doc: Check the spelling and capitalization of the file name and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-269 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified log file is part of thread %s not %s |
| Long Text: | The given redo log file is not part of the given thread. |
| Repair Text: | From Oracle doc: Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error creating archive log %s |
| Long Text: | An error was encountered when either creating or opening the destination file for archiving. |
| Repair Text: | From Oracle doc: Check that the archive destination is valid and that there is sufficient space on the destination device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | there are no logs that need archiving |
| Long Text: | An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-272 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error writing archive log %s |
| Long Text: | An I/O error occurred while archiving a redo log file. |
| Repair Text: | From Oracle doc: Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-273 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | media recovery of direct load data that was not logged |
| Long Text: | A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt. |
| Repair Text: | From Oracle doc: The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-274 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | illegal recovery option %s |
| Long Text: | An illegal option was specified for a recovery command. |
| Repair Text: | From Oracle doc: Correct the syntax and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-275 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | media recovery has already been started |
| Long Text: | An attempt was made to start a second media recovery operation in the same session. |
| Repair Text: | From Oracle doc: Complete or cancel the first media recovery session or start another session to perform media recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CHANGE keyword specified but no change number given |
| Long Text: | The CHANGE keyword was specified on the command line, but no change number was given. |
| Repair Text: | From Oracle doc: Retry the command using a valid change number after the CHANGE keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-277 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | illegal option to the UNTIL recovery flag %s |
| Long Text: | Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-278 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | log file '%s' no longer needed for this recovery |
| Long Text: | The specified redo log file is no longer needed for the current recovery. |
| Repair Text: | From Oracle doc: No action is required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-279 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | change %s generated at %s needed for thread %s |
| Long Text: | The requested log is required to proceed with recovery. |
| Repair Text: | From Oracle doc: Supply the requested log with ALTER DATABASE RECOVER LOGFILE filename or cancel recovery with ALTER DATABASE RECOVER CANCEL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-280 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | change %s for thread %s is in sequence #%s |
| Long Text: | This message helps to locate the redo log file with the specified change number requested by other messages. |
| Repair Text: | From Oracle doc: Use the information provided in this message to specify the required archived redo log files for other errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | media recovery may not be performed using dispatcher |
| Long Text: | An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method. |
| Repair Text: | From Oracle doc: Connect to the instance via a dedicated server process to perform media recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-282 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | UPI %s call not supported, use ALTER DATABASE RECOVER |
| Long Text: | The given UPI call is no longer supported. |
| Repair Text: | From Oracle doc: Use the ALTER DATABASE RECOVER command for all recovery actions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-283 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | recovery session canceled due to errors |
| Long Text: | An error during recovery was determined to be fatal enough to end the current recovery session. |
| Repair Text: | From Oracle doc: More specific messages will accompany this message. Refer to the other messages for the appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-284 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | recovery session still in progress |
| Long Text: | An error during recovery was determined to be minor enough to allow the current recovery session to continue. |
| Repair Text: | From Oracle doc: More specific messages will accompany this message. Refer to the other messages for the appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-285 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | TIME not given as a %s constant |
| Long Text: | UNTIL TIME was not followed by a string constant for the time. |
| Repair Text: | From Oracle doc: Enter the time enclosed in single quotation marks. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-286 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no members available, or no member contains valid data |
| Long Text: | None of the members of a redo log file group are available, or the available members do not contain complete data. |
| Repair Text: | From Oracle doc: If a member is temporarily offline, attempt to make it available. Make sure that the correct file names are being used, especially if the redo log file is being accessed from a remote location. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-287 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified change number %s not found in thread %s |
| Long Text: | The given change number does not appear in any of the online redo logs for the given thread. |
| Repair Text: | From Oracle doc: Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-288 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | to continue recovery type ALTER DATABASE RECOVER CONTINUE |
| Long Text: | During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors. |
| Repair Text: | From Oracle doc: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-289 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | suggestion : %s |
| Long Text: | This message reports the next redo log file name that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived. |
| Repair Text: | From Oracle doc: Consider using this file name for the next log needed for recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operating system archival error occurred. See error below |
| Long Text: | While attempting to archive to a redo log file, the server encountered an unexpected operating system error. |
| Repair Text: | From Oracle doc: Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-291 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | numeric value required for PARALLEL option |
| Long Text: | A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism. |
| Repair Text: | From Oracle doc: Re-enter the command with a numeric argument specifying the degree of parallelism desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-292 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | parallel recovery feature not installed |
| Long Text: | A parallel recovery was requested when the parallel recovery option is not installed. |
| Repair Text: | From Oracle doc: Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-293 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | controlfile out of sync with redo log |
| Long Text: | The redo log file and control file are out of sync because a non-current control file was specified when the instance was started. |
| Repair Text: | From Oracle doc: Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-294 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid archivelog format specifier '%s' |
| Long Text: | An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted for string are s, S, t, and T. |
| Repair Text: | From Oracle doc: Correct the initialization file and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-295 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | datafile number %s is invalid, must be between 1 and %s |
| Long Text: | An invalid file number was specified. |
| Repair Text: | From Oracle doc: Specify a correct datafile number and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-296 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of files (%s) exceeded for RECOVER DATAFILE LIST |
| Long Text: | The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than Recovery Manager needs to recover to satisfy the user's RECOVER command. |
| Repair Text: | From Oracle doc: Restart the instance with a higher value for DB_FILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-297 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START |
| Long Text: | The RECOVER DATAFILE START command was issued, but no RECOVER DATAFILE LIST commands had been issued. This only happens when doing recovery with Recovery Manager, and is an internal error in Recovery Manager, because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-298 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Missing or invalid TIMEOUT interval |
| Long Text: | A non-zero integer timeout interval (in minutes) must be specified after the TIMEOUT keyword. |
| Repair Text: | From Oracle doc: Correct the syntax and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal redo log block size %s specified - exceeds limit of %s |
| Long Text: | The specified block size of the redo log is greater than the maximum block size for the operating system. |
| Repair Text: | From Oracle doc: Create the redo log on a device with a smaller block size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in adding log file '%s' - file cannot be created |
| Long Text: | The creation of the redo log file failed |
| Repair Text: | From Oracle doc: Check whether: There is enough storage space on the device The name of the file is valid The device is online An I/O error occurred Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | limit of %s logs exceeded |
| Long Text: | The maximum number of redo log files has been exceeded. There is a limit, set at database creation, on the number of redo log files (typically 16). |
| Repair Text: | From Oracle doc: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | requested INSTANCE_NUMBER is busy |
| Long Text: | An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use. |
| Repair Text: | From Oracle doc: Either: Specify another INSTANCE_NUMBER, Shut down the running instance with this number, or Wait for instance recovery to complete on the instance with this number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s inconsistent; belongs to another database |
| Long Text: | The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database. |
| Repair Text: | From Oracle doc: Specify the correct redo log file, and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | limit of %s instances in this database |
| Long Text: | Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances. |
| Repair Text: | From Oracle doc: You cannot start more than the lower of: the operating system-specific maximum or the number of instances specified by the MAXINSTANCES option specified in the CREATE DATABASE statement |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-307 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | requested INSTANCE_NUMBER out of range, maximum is %s |
| Long Text: | The initialization parameter INSTANCE_NUMBER specified a number that was out of range. |
| Repair Text: | From Oracle doc: Change the value of INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is 1 and the maximum value is the lower of the operating system-specific maximum or the value of the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-308 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot open archived log '%s' |
| Long Text: | The system cannot access a required archived redo log file. |
| Repair Text: | From Oracle doc: Check that the offline log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log belongs to wrong database |
| Long Text: | The system cannot access the archived redo log because it belongs to another database. |
| Repair Text: | From Oracle doc: Specify the correct redo log file and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log contains sequence %s; sequence %s required |
| Long Text: | The archived log is out of sequence, probably because it is corrupted or the wrong redo log file name was specified during recovery. |
| Repair Text: | From Oracle doc: Specify the correct redo log file and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot read header from archived log |
| Long Text: | An I/O error occurred when attempting to read the log file header from the specified archived redo log file. |
| Repair Text: | From Oracle doc: Other messages will accompany this message. See the associated messages for the appropriate action to take. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-312 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | online log %s thread %s: '%s' |
| Long Text: | This message reports the file name for details of another message. |
| Repair Text: | From Oracle doc: Other messages will accompany this message. See the associated messages for the appropriate action to take. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | open failed for members of log group %s of thread %s |
| Long Text: | The online log cannot be opened. The file may not be in the expected location. |
| Repair Text: | From Oracle doc: Specify the correct redo log file or make the log available, if necessary. Also, see the accompanying messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, expected sequence# %s doesn't match %s |
| Long Text: | The online log is corrupted or is an old version. |
| Repair Text: | From Oracle doc: Find and install the correct version of the log or reset the logs. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, wrong thread # %s in header |
| Long Text: | The online log is corrupted or is an old version. |
| Repair Text: | From Oracle doc: Find and install the correct version of the log or reset the logs. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, type %s in header is not log file |
| Long Text: | The online log is corrupted or is an old version. |
| Repair Text: | From Oracle doc: Find and install the correct version of the log or reset the logs. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file type %s in header is not log file |
| Long Text: | This is not an archived log file. |
| Repair Text: | From Oracle doc: Find the correct file and try again. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, expected file size %s doesn't match %s |
| Long Text: | The file size indicated in the control file did not match the file size contained in the log file. |
| Repair Text: | From Oracle doc: Restore the correct file or reset the logs. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s has incorrect log reset status |
| Long Text: | An online redo log has log reset data that is different from the log reset data in the control file. The log is probably an incorrectly restored backup. |
| Repair Text: | From Oracle doc: Restore the correct file or reset the logs. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-320 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot read file header from log %s of thread %s |
| Long Text: | The file is not available. |
| Repair Text: | From Oracle doc: Restore the log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, cannot update log file header |
| Long Text: | Cannot write to the log file. |
| Repair Text: | From Oracle doc: Restore access to the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s is not current copy |
| Long Text: | An online log appears to be an incorrectly restored backup. |
| Repair Text: | From Oracle doc: Restore the correct file or reset the logs. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-323 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Current log of thread %s not useable and all others need archiving |
| Long Text: | An attempt to open the thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used. |
| Repair Text: | From Oracle doc: Archive the logs for the thread and then retry the open. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-324 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log file '%s' translated name '%s' too long, %s characters exceeds %s limit |
| Long Text: | The translated name for a log file is too long. |
| Repair Text: | From Oracle doc: Choose an untranslated name that yields a shorter translated name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-325 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log for thread %s, wrong thread # %s in header |
| Long Text: | The archived log is corrupted or for another thread. Cannot use the log for applying the redo. |
| Repair Text: | From Oracle doc: Find the correct archived log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-326 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log begins at change %s, need earlier change %s |
| Long Text: | The archived log supplied for recovery was generated after the log that is needed. Cannot yet use the log for applying redo. |
| Repair Text: | From Oracle doc: Find the correct archived log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-327 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, physical size %s less than needed %s |
| Long Text: | A log file has shrunk in size. This is likely to have been caused by a computer operator's mistake or an operating system error. |
| Repair Text: | From Oracle doc: Restore the log file from backup. If a backup is not available, drop this log and re-create it. If the database was shut down cleanly, no further action should be required; otherwise, incomplete recovery may be required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-328 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log ends at change %s, need later change %s |
| Long Text: | The archived log supplied for recovery was generated before the log that is needed. Cannot use the log for applying redo. |
| Repair Text: | From Oracle doc: Find the correct archived log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-329 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log begins at change %s, need change %s |
| Long Text: | The archived log is not the correct log. An earlier log is needed. |
| Repair Text: | From Oracle doc: Restore the correct log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-330 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log ends at change %s, need change %s |
| Long Text: | The archived log is not the correct log. A later log is needed. |
| Repair Text: | From Oracle doc: Restore the correct log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-331 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log version %s incompatible with ORACLE version %s |
| Long Text: | The log was written by an incompatible version of Oracle. |
| Repair Text: | From Oracle doc: Recover the database with the compatible software, shut it down cleanly, and then restart Oracle with the current software. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-332 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log is too small - may be incompletely archived |
| Long Text: | The log is smaller than the space allocated in it. May be the result of a SHUTDOWN ABORT while it was being written by the archiver. |
| Repair Text: | From Oracle doc: Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-333 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | redo log read error block %s count %s |
| Long Text: | An I/O error occurred while reading the log described in the accompanying error. |
| Repair Text: | From Oracle doc: Restore accessibility to file, or get another copy of the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-334 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | archived log: '%s' |
| Long Text: | This message reports the file name involved with other errors. |
| Repair Text: | From Oracle doc: See associated error messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | online log %s: No log with this number, log does not exist |
| Long Text: | This message reports the file name involved with other errors. |
| Repair Text: | From Oracle doc: See associated error messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-336 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log file size %s blocks is less than minimum %s blocks |
| Long Text: | The log file size as specified in the CREATE DATABASE statement is too small. |
| Repair Text: | From Oracle doc: Increase the log file size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-337 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log file '%s' does not exist and no size specified |
| Long Text: | An attempt to add a log found neither an existing file nor a size for creating the file. |
| Repair Text: | From Oracle doc: Specify a size for the log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-338 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s is more recent than controlfile |
| Long Text: | The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough. |
| Repair Text: | From Oracle doc: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-339 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log does not contain any redo |
| Long Text: | The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log. |
| Repair Text: | From Oracle doc: Restore the correct log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IO error processing online log %s of thread %s |
| Long Text: | An I/O error occurred on the named online log. |
| Repair Text: | From Oracle doc: Restore accessibility to the file or restore the file from backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, wrong log # %s in header |
| Long Text: | The internal information in an online log file does not match the control file. |
| Repair Text: | From Oracle doc: Restore the correct file or reset the logs. Refer to the Oracle8i Administrator's Guide for recovery procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log was created before last RESETLOGS |
| Long Text: | Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo. |
| Repair Text: | From Oracle doc: Supply the correct log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-343 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many errors, log member closed |
| Long Text: | The maximum number of errors on this log member has been exceeded. |
| Repair Text: | From Oracle doc: Correct the underlying problem by referring to the other error messages found with this one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to re-create online log '%s' |
| Long Text: | An I/O failure occurred when attempting to re-create an online log as part of either an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command. |
| Repair Text: | From Oracle doc: Correct the file/device as indicated by accompanying errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | redo log write error block %s count %s |
| Long Text: | An I/O error occurred while writing the log. |
| Repair Text: | From Oracle doc: Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-346 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log member marked as STALE |
| Long Text: | A log file member no longer is complete. |
| Repair Text: | From Oracle doc: Correct the underlying problem by referring to the other error messages found with this one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-347 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, expected block size %s doesn't match %s |
| Long Text: | During online recovery, the block size specified in the control file did not match the block size contained in the redo log file. |
| Repair Text: | From Oracle doc: Restore the correct redo file from a backup or reset the online redo log files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-348 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | single-process redo failure. Must abort instance |
| Long Text: | A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation. |
| Repair Text: | From Oracle doc: SHUTDOWN ABORT and restart the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-349 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure obtaining block size for '%s' |
| Long Text: | The operating system was unable to determine the block size for the given file name. |
| Repair Text: | From Oracle doc: Consult the accompanying error message, and correct the device or specify another file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-350 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | log %s of thread %s needs to be archived |
| Long Text: | The command cannot be done because the log has not been archived, and media recovery has been enabled. |
| Repair Text: | From Oracle doc: Archive the log or disable media recovery. If the command supports an UNARCHIVED option, then it can be used. However, this may result in making backups unusable, and forcing the drop of some offline files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recover-to time invalid |
| Long Text: | The time specified in a recover-until statement must be after January 1st 1988. |
| Repair Text: | From Oracle doc: Specify a time after January 1st 1988. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | all logs for thread %s need to be archived - cannot enable |
| Long Text: | An attempt was made to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread. |
| Repair Text: | From Oracle doc: Archive a log for the thread or disable media recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log corruption near block %s change %s time %s |
| Long Text: | Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption. |
| Repair Text: | From Oracle doc: Perform recovery with a good version of the redo log or do incomplete recovery up to the indicated change or time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | corrupt redo log block header |
| Long Text: | The block header on the redo block indicated by the accompanying error is not valid. The block number and time-stamp are given in an accompanying message. |
| Repair Text: | From Oracle doc: Perform recovery with a good version of the redo log or perform cancel-based recovery up to, but not including, the corrupted redo log file. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-355 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | change numbers out of order |
| Long Text: | A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one. |
| Repair Text: | From Oracle doc: Perform recovery with a good version of the log or perform time-based recovery up to the indicated time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-356 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inconsistent lengths in change description |
| Long Text: | A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way. |
| Repair Text: | From Oracle doc: Perform recovery with a good version of the log or do time-based recovery up to the indicated time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-357 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many members specified for log file, the maximum is %s |
| Long Text: | An ADD LOGFILE or ADD LOGFILE MEMBER command would result in a log with too many members. The number of members is set when the database is created. |
| Repair Text: | From Oracle doc: Use fewer log file members. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-358 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Too many file members specified, the maximum is %s |
| Long Text: | A CREATE or ALTER statement specified too many members in a parenthesised file list. |
| Repair Text: | From Oracle doc: Specify a number of file members that is within the port-defined limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-359 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logfile group %s does not exist |
| Long Text: | An ADD LOGFILE MEMBER or DROP LOGFILE request specified a log file group number that does not exist. |
| Repair Text: | From Oracle doc: Check the configuration of the log files and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a logfile member: %s |
| Long Text: | A file name was given to DROP LOGFILE MEMBER command that is not a part of the database, or which is a datafile. |
| Repair Text: | From Oracle doc: Supply a valid log file member name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot remove last log member %s for group %s |
| Long Text: | An attempt has been made to remove the last member of a log file group. |
| Repair Text: | From Oracle doc: If desired, delete the entire log, by using DROP LOGFILE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | member is required to form a valid logfile in group %s |
| Long Text: | A request to drop a log file member was denied because it would remove data required to form a complete log file. |
| Repair Text: | From Oracle doc: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log is not the archived version |
| Long Text: | The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command. |
| Repair Text: | From Oracle doc: Find the archived version of the log and supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-364 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot write header to new log member |
| Long Text: | An I/O error occurred when attempting to write the header to a log member that is being added to an existing group. |
| Repair Text: | From Oracle doc: See accompanying errors. Fix the problem or use another file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-365 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified log is not the correct next log |
| Long Text: | The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database. |
| Repair Text: | From Oracle doc: Find the log that was generated by this copy of the database and give that file name to recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-366 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s, checksum error in the file header |
| Long Text: | The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted. |
| Repair Text: | From Oracle doc: Find and install correct version of the log or reset the logs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-367 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | checksum error in log file header |
| Long Text: | The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted. |
| Repair Text: | From Oracle doc: Find the correct file and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-368 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | checksum error in redo log block |
| Long Text: | The redo block indicated by the accompanying error, is not valid. It has a checksum that does not match the block contents. |
| Repair Text: | From Oracle doc: Perform recovery with a good version of the log or do time-based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. Restore the correct file or reset logs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Current log of thread %s not useable and other log being cleared |
| Long Text: | An attempt to open the thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used. |
| Repair Text: | From Oracle doc: If the ALTER DATABASE CLEAR LOGFILE command is still active, then wait for it to complete. Otherwise, reissue the CLEAR command. If there are other online logs for the thread that are not being cleared, then archive the logs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-371 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no free buffer handles available |
| Long Text: | There is not enough memory to proceed with the operation. |
| Repair Text: | From Oracle doc: Raise the value of the SHARED_POOL_SIZE initialization parameter and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-372 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s cannot be modified at this time |
| Long Text: | An attempt was made to modify the contents of a file that cannot be modified. The file is most likely part of a read-only tablespace but may be in the process of going offline, or the database may be in the process of closing. |
| Repair Text: | From Oracle doc: Check the status of the file and its tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-373 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | online log version %s incompatible with ORACLE version %s |
| Long Text: | The online log was written by an incompatible version of Oracle. This can occur when the log file was created by either a new or older version of Oracle. |
| Repair Text: | From Oracle doc: Recover the database with the compatible software, shut it down cleanly, and then restart with current software. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-374 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter db_block_size = %s invalid, valid range [%s..%s] |
| Long Text: | An invalid value was specified for the DB_BLOCK_SIZE parameter. |
| Repair Text: | From Oracle doc: Adjust the value of the parameter and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-375 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to get default db_block_size |
| Long Text: | The system was unable to determine the default value for DB_BLOCK_SIZE. |
| Repair Text: | From Oracle doc: See the accompanying system-specific error. As a workaround, specify the block size in the INIT.ORA file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-376 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s cannot be read at this time |
| Long Text: | An attempt was made to read from a file that is not readable. Most likely the file is offline. |
| Repair Text: | From Oracle doc: Check the state of the file. Bring it online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-377 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Frequent backups of file %s causing write operation to stall |
| Long Text: | Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete. |
| Repair Text: | From Oracle doc: Increase the interval between begin hot-backup commands for this file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-378 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buffer pools cannot be created as specified |
| Long Text: | The number of buffers or the number of LRU latches is too small to satisfy the specified buffer pool configuration. |
| Repair Text: | From Oracle doc: Either increase the number of buffers and/or number of LRU latches or configure smaller buffer pools. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-379 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no free buffers available in buffer pool %s |
| Long Text: | All buffers in the specified buffer pool are in use and no free buffers are available. |
| Repair Text: | From Oracle doc: Increase the number of buffers in the specified pool. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-390 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | log %s of thread %s is being cleared, cannot become current log |
| Long Text: | An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be usable when the clearing completes. The command that began the clearing may have terminated without completing the clearing. |
| Repair Text: | From Oracle doc: If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command, or drop the log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-391 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | All threads must switch to new log format at the same time |
| Long Text: | An attempt to switch the current log of a single thread is not allowed because the compatibility requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time. |
| Repair Text: | From Oracle doc: Open the database to cause the coordinated log switch. If that is not possible, then return to the same software version and compatibility setting last used to open the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-392 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s is being cleared, operation not allowed |
| Long Text: | An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing. |
| Repair Text: | From Oracle doc: If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command or drop the log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-393 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s of thread %s is needed for recovery of offline datafiles |
| Long Text: | Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared, the tablespaces containing the files will have to be dropped. |
| Repair Text: | From Oracle doc: Archive the log and then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-394 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | online log reused while attempting to archive it |
| Long Text: | An attempt was made to reuse an online log file that is being archived. |
| Repair Text: | From Oracle doc: The online log file has been overwritten; it cannot be archived. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-395 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | online logs for the clone database must be renamed |
| Long Text: | A clone database open forces log file renaming to avoid overwriting the primary log files. |
| Repair Text: | From Oracle doc: Rename the log files manually or using the LOG_FILE_NAME_CONVERT initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid release value %s for parameter %s |
| Long Text: | The release level given for the specified initialization parameter is invalid. |
| Repair Text: | From Oracle doc: Correct the parameter value in the parameter file and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the value for parameter %s is not supported by this release |
| Long Text: | The value specified cannot be supported by this release of the software. |
| Repair Text: | From Oracle doc: Choose an appropriate value, or remove the parameter value to use the default value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database changes by release %s cannot be used by release %s |
| Long Text: | Changes have been made to the database that require a newer software release or that violate the compatibility parameters. |
| Repair Text: | From Oracle doc: Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s (%s) is not the same as other instances (%s) |
| Long Text: | Another instance has set the COMPATIBLE or COMPATIBLE NO RECOVERY parameters differently than this instance. |
| Repair Text: | From Oracle doc: Change the parameters of the current instance to match other instances already running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Convert file not found: '%s' |
| Long Text: | The file used for converting the database from V7 to V8 could not be found. |
| Repair Text: | From Oracle doc: Verify that the migration process has been started on this database and that the convert file name is accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-405 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | compatibility type "%s" |
| Long Text: | Reporting a type associated with another error. |
| Repair Text: | From Oracle doc: See the accompanying error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | COMPATIBLE parameter needs to be %s or greater |
| Long Text: | The value of the COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter. |
| Repair Text: | From Oracle doc: Shut down and restart with a higher compatibility setting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rolling upgrade from release %s.%s to %s.%s is not allowed |
| Long Text: | Another instance executing software at a different point release already has the database mounted. |
| Repair Text: | From Oracle doc: Shut down all instances then restart with the new software. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s is set to TRUE |
| Long Text: | Reporting the parameter that resulted in the compatibility error. |
| Repair Text: | From Oracle doc: Shut down and restart with a higher compatibility setting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE is not licensed. Contact Oracle Corp. for assistance |
| Long Text: | This installed Oracle software is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes. |
| Repair Text: | From Oracle doc: Check that Oracle is installed correctly. Then contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE feature is not licensed. Contact Oracle Corp. for assistance |
| Long Text: | This installed Oracle feature is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes. |
| Repair Text: | From Oracle doc: Check that Oracle is installed correctly. Then contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s Option not installed |
| Long Text: | The specified option is not installed. |
| Repair Text: | From Oracle doc: Either avoid calling the option, or purchase and install the option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-439 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | feature not enabled: %s |
| Long Text: | The specified feature is not enabled. |
| Repair Text: | From Oracle doc: Do not attempt to use this feature. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | background process "%s" did not start |
| Long Text: | The specified process did not start. |
| Repair Text: | From Oracle doc: Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | background process "%s" failed while starting |
| Long Text: | Usually due to a bad (or non-existent) background process image. |
| Repair Text: | From Oracle doc: Get a good background process image. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-445 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | background process "%s" did not start after %s seconds |
| Long Text: | The specified process did not start after the specified time. |
| Repair Text: | From Oracle doc: Ensure that the background did not die and leave a trace file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | background process started when not expected |
| Long Text: | The background process specified started after Oracle was already running. |
| Repair Text: | From Oracle doc: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. If no user on site started the process, report the message to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-447 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | fatal error in background process |
| Long Text: | One of the background processes died unexpectedly. |
| Repair Text: | From Oracle doc: Restart the system. Check and, if necessary, correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-448 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | normal completion of background process |
| Long Text: | One of the background processes completed normally as requested by the user. |
| Repair Text: | From Oracle doc: If you are solving a problem, check for other messages and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | background process '%s' unexpectedly terminated with error %s |
| Long Text: | A foreground process needing service from a background process has discovered the process died. |
| Repair Text: | From Oracle doc: Refer to the message code given in the message and the trace file for the foreground and the background processes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-470 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LGWR process terminated with error |
| Long Text: | The Log Writer process terminated abnormally. |
| Repair Text: | From Oracle doc: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-471 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBWR process terminated with error |
| Long Text: | The Database Writer process terminated abnormally. |
| Repair Text: | From Oracle doc: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-472 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PMON process terminated with error |
| Long Text: | The Process Monitor process terminated abnormally. |
| Repair Text: | From Oracle doc: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-473 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ARCH process terminated with error |
| Long Text: | The Archiver process terminated abnormally. |
| Repair Text: | From Oracle doc: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-474 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SMON process terminated with error |
| Long Text: | The System Monitor process terminated abnormally. |
| Repair Text: | From Oracle doc: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-475 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TRWR process terminated with error |
| Long Text: | The system tracing process terminated abnormally. |
| Repair Text: | From Oracle doc: Restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-476 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RECO process terminated with error |
| Long Text: | The distributed transaction (two-phase commit) recovery process terminated abnormally. |
| Repair Text: | From Oracle doc: Restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-477 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SNP* process terminated with error |
| Long Text: | A snapshot refresh process terminated abnormally. |
| Repair Text: | From Oracle doc: Restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-480 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LCK* process terminated with error |
| Long Text: | One Lock process terminated abnormally. |
| Repair Text: | From Oracle doc: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-481 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LMON process terminated with error |
| Long Text: | The Lock Manager monitor process terminated abnormally. |
| Repair Text: | From Oracle doc: Restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-482 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LMD* process terminated with error |
| Long Text: | A Lock Manager daemon process terminated abnormally. |
| Repair Text: | From Oracle doc: Restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-483 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | During shutdown a process abnormally terminated |
| Long Text: | One of the background processes did not exit normally at or near the time of shutdown. |
| Repair Text: | From Oracle doc: Use the SHUTDOWN ABORT command. Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-568 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Maximum number of interrupt handlers exceeded |
| Long Text: | The number of registered interrupt handling routines for when the break key is entered exceeds the maximum allowed. |
| Repair Text: | From Oracle doc: Reduce the number of registered interrupt handlers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s] |
| Long Text: | This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include: timeouts file corruption failed data checks in memory hardware, memory, or I/O errors incorrectly restored files The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle. |
| Repair Text: | From Oracle doc: Report this error to Oracle Customer Support after gathering the following information: events that led up to the error the operations that were attempted that led to the error the conditions of the operating system and databases at the time of the error any unusual circumstances that occurred before receiving the ORA-00600 message contents of any trace files generated by the error the relevant portions of the Alter files Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cleanup lock conflict |
| Long Text: | The Process Monitor encountered a lock conflict while trying to recover processes. This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-602 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal programming exception |
| Long Text: | Internal programming exception occurred. |
| Repair Text: | From Oracle doc: Report this error as a program bug to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-603 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | ORACLE server session terminated by fatal error |
| Long Text: | An Oracle Server session is in an unrecoverable state. |
| Repair Text: | From Oracle doc: Log in to Oracle again so a new server session will be created automatically. Examine the session trace file for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-604 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred at recursive SQL level %s |
| Long Text: | An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables). |
| Repair Text: | From Oracle doc: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Internal error code |
| Long Text: | A call to deferred UPI functions was made in non-deferred mode. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object necessary for warmstarting database cannot be altered |
| Long Text: | An attempt was made to alter or drop a database object (table, cluster, or index) defined in the control file's bootstrap segment and needed to warm start the database. |
| Repair Text: | From Oracle doc: Correct the spelling of the object name or remove it from the ALTER or DROP statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bootstrap verison '%s' inconsistent with version '%s' |
| Long Text: | The version of the bootstrap data is incompatible with the current version of the software. |
| Repair Text: | From Oracle doc: Restore a version of the software that is compatible with the datafiles. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of row cache instance locks exceeded |
| Long Text: | There are not enough row cache enqueues. |
| Repair Text: | From Oracle doc: Increase the value of the ROW CACHE ENQUEUE parameter and restart the system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bootstrap process failure |
| Long Text: | Failure in processing bootstrap data. Refer to the accompanying messages for more information about the cause of the problem. |
| Repair Text: | From Oracle doc: Correct the problems mentioned in the other messages. If the problem persists, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inconsistent state during start up; shut down the instance, then restart it |
| Long Text: | A previous attempt to start an instance was terminated. |
| Repair Text: | From Oracle doc: Shut down the instance completely and then restart it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error message translation failed |
| Long Text: | There is an internal error where a routine was unable to translate a message code. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-900 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid SQL statement |
| Long Text: | The statement is not recognized as a valid SQL statement. This error can occur if the Procedural Option is not installed and a SQL statement is issued that requires this option (for example, a CREATE PROCEDURE statement). You can determine if the Procedural Option is installed by starting SQL*Plus. If the PL/SQL banner is not displayed, then the option is not installed. |
| Repair Text: | From Oracle doc: Correct the syntax or install the Procedural Option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-901 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid CREATE command |
| Long Text: | The CREATE command was not followed by a valid CREATE option. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-902 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid datatype |
| Long Text: | The datatype entered in the CREATE or ALTER TABLE statement is not valid. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-903 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid table name |
| Long Text: | A table or cluster name is invalid or does not exist. This message is also issued if an invalid cluster name or no cluster name is specified in an ALTER CLUSTER or DROP CLUSTER statement. |
| Repair Text: | From Oracle doc: Check spelling. A valid table name or cluster name must begin with a letter and may contain only alphanumeric characters and the special characters $, _, and #. The name must be less than or equal to 30 characters and cannot be a reserved word. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-904 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid column name |
| Long Text: | The column name entered is either missing or invalid. |
| Repair Text: | From Oracle doc: Enter a valid column name. A valid column name must begin with a letter, be less than or equal to 30 characters, and consist of only alphanumeric characters and the special characters $, _, and #. If it contains other characters, it must be enclosed in double quotation marks. It may not be a reserved word. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-905 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing keyword |
| Long Text: | A required keyword is missing. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-906 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing left parenthesis |
| Long Text: | A required left parenthesis has been omitted. Certain commands, such as CREATE TABLE, CREATE CLUSTER, and INSERT, require a list of items enclosed in parentheses. Parentheses also are required around subqueries in WHERE clauses and in UPDATE table SET column = (SELECT...) statements. |
| Repair Text: | From Oracle doc: Correct the syntax, inserting a left parenthesis where required, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-907 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing right parenthesis |
| Long Text: | A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs. |
| Repair Text: | From Oracle doc: Correct the syntax and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-908 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing NULL keyword |
| Long Text: | Either of the following: In a CREATE TABLE or ALTER TABLE statement, NOT was entered to specify that no null values are allowed in that column, but the keyword NULL was omitted. In the IS [NOT] NULL logical operator, the keyword NULL was not found. For example, the following statement generates this message: SELECT * FROM EMP WHERE DEPTNO IS NOT;
|
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-909 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid number of arguments |
| Long Text: | An Oracle function was referenced with an incorrect number of arguments. All Oracle functions, except for SYSDATE, require at least one argument. |
| Repair Text: | From Oracle doc: Correct the syntax of the function by entering the required number of arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-910 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | specified length too long for its datatype |
| Long Text: | No size was specified for a character field or the size was invalid. A maximum length must be specified for each character column. The maximum value for this length varies for each character datatype, such as CHAR or VARCHAR2. |
| Repair Text: | From Oracle doc: Enter a maximum length for the field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-911 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid character |
| Long Text: | Special characters are valid only in certain places. If special characters other than $, _, and # are used in a name and the name is not enclosed in double quotation marks ("), this message will be issued. One exception to this rule is for database names; in this case, double quotes are stripped out and ignored. |
| Repair Text: | From Oracle doc: Remove the invalid character from the statement or enclose the object name in double quotation marks. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-913 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | too many values |
| Long Text: | The SQL statement requires two sets of values equal in number. This error occurs when the second set contains more items than the first set. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in the INSERT. |
| Repair Text: | From Oracle doc: Check the number of items in each set and change the SQL statement to make them equal. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-914 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing ADD keyword |
| Long Text: | The keyword ADD does not precede one of the following: The keyword log file in an ALTER DATABASE statement A column element or table constraint in an ALTER TABLE statement The keyword DATAFILE in an ALTER TABLESPACE statement |
| Repair Text: | From Oracle doc: Specify the keyword ADD in the ALTER statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-915 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | network access of dictionary table not currently allowed |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-917 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing comma |
| Long Text: | A required comma has been omitted from a list of columns or values in an INSERT statement or a list of the form ((C,D),(E,F), ...). |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-918 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | column ambiguously defined |
| Long Text: | A column name used in a join exists in more than one table and is thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO. |
| Repair Text: | From Oracle doc: Prefix references to column names that exist in multiple tables with either the table name or a table alias and a period (.), as in the examples above. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-919 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid function |
| Long Text: | An entry was formatted like a function call, but it is not recognizable as an Oracle function. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-920 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid relational operator |
| Long Text: | A search condition was entered with an invalid or missing relational operator. |
| Repair Text: | From Oracle doc: Include a valid relational operator such as =, !=, ^=, <>, >, <, >=, <=, ALL, ANY, [NOT] BETWEEN, EXISTS, [NOT] IN, IS [NOT] NULL, or [NOT] LIKE in the condition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-921 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | unexpected end of SQL command |
| Long Text: | The SQL command was not complete. Part of a valid command was entered, but at least one major component was omitted. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-922 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing or invalid option |
| Long Text: | An invalid option was specified in defining a column or storage clause. The valid option in specifying a column is NOT NULL to specify that the column cannot contain any NULL values. Only constraints may follow the datatype. Specifying a maximum length on a DATE or LONG datatype also causes this error. |
| Repair Text: | From Oracle doc: Correct the syntax. Remove the erroneous option or length specification from the column or storage specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-923 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | FROM keyword not found where expected |
| Long Text: | In a SELECT or REVOKE statement, the keyword FROM was either missing, misplaced, or misspelled. The keyword FROM must follow the last selected item in a SELECT statement or the privileges in a REVOKE statement. |
| Repair Text: | From Oracle doc: Correct the syntax. Insert the keyword FROM where appropriate. The SELECT list itself also may be in error. If quotation marks were used in an alias, check that double quotation marks enclose the alias. Also, check to see if a reserved word was used as an alias. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-924 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing BY keyword |
| Long Text: | The keyword BY was omitted in a GROUP BY, ORDER BY, or CONNECT BY clause. In a GRANT statement, the keyword IDENTIFIED must also be followed by the keyword BY. |
| Repair Text: | From Oracle doc: Correct the syntax. Insert the keyword BY where required and then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-925 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing INTO keyword |
| Long Text: | An INSERT statement has been entered without the keyword INTO. |
| Repair Text: | From Oracle doc: Correct the syntax. Insert the keyword INTO where required and then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-926 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing VALUES keyword |
| Long Text: | An INSERT statement has been entered without the keyword VALUES or SELECT. Either a VALUES clause or a SELECT subquery must follow the INSERT INTO clause. |
| Repair Text: | From Oracle doc: Correct the syntax. Enter either a VALUES clause or a subquery after the INSERT INTO clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-927 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing equal sign |
| Long Text: | An equal sign has been omitted in one of the following places: In the SET clause of an UPDATE statement Following "!" in a search condition to signify not equal |
| Repair Text: | From Oracle doc: Correct the syntax. Insert the equal sign where required and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-928 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing SELECT keyword |
| Long Text: | A SELECT subquery must be included in a CREATE VIEW statement. |
| Repair Text: | From Oracle doc: Correct the syntax. Insert the required SELECT clause after the CREATE VIEW clause and then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-929 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing period |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-930 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing asterisk |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-931 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing identifier |
| Long Text: | The specified string does not contain an identifier. |
| Repair Text: | From Oracle doc: Correct the string argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-932 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inconsistent datatypes |
| Long Text: | One of the following: An attempt was made to perform an operation on incompatible datatypes. For example, adding a character field to a date field (dates may only be added to numeric fields) or concatenating a character field with a long field. An attempt was made to perform an operation on a database object (such as a table or view) that is not intended for normal use. For example, system tables cannot be modified by a user. Note that on rare occasions this error occurs because a misspelled object name matched a restricted object's name. An attempt was made to use an undocumented view. |
| Repair Text: | From Oracle doc: If the cause is different datatypes, then use consistent datatypes. For example, convert the character field to a numeric field with the TO_NUMBER function before adding it to the date field. Functions may not be used with long fields. an object not intended for normal use, then do not access the restricted object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-933 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | SQL command not properly ended |
| Long Text: | The SQL statement ends with an inappropriate clause. For example, an ORDER BY clause may have been included in a CREATE VIEW or INSERT statement. ORDER BY cannot be used to create an ordered view or to insert in a certain order. Also, an improper SQL ending occurs if IN clause is used with only one argument (IN(X), for example). An IN clause must have two or more arguments. |
| Repair Text: | From Oracle doc: Correct the syntax by removing the inappropriate clauses. It may be possible to duplicate the removed clause with another SQL statement. For example, to order the rows of a view, do so when querying the view and not when creating it. This error can also occur in SQL*Forms applications if a continuation line is indented. Check for indented lines and delete these spaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-934 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | group function is not allowed here |
| Long Text: | One of the group functions, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used in a WHERE or GROUP BY clause. |
| Repair Text: | From Oracle doc: Remove the group function from the WHERE or GROUP BY clause. The desired result may be achieved by including the function in a subquery or HAVING clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-935 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | group function is nested too deeply |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-936 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing expression |
| Long Text: | A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message is also issued in cases where a reserved word is misused, as in SELECT TABLE. |
| Repair Text: | From Oracle doc: Check the statement syntax and specify the missing component. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-937 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a single-group group function |
| Long Text: | A SELECT list cannot include both a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, and an individual column expression, unless the individual column expression is included in a GROUP BY clause. |
| Repair Text: | From Oracle doc: Drop either the group function or the individual column expression from the SELECT list or add a GROUP BY clause that includes all individual column expressions listed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-938 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | not enough arguments for function |
| Long Text: | The function was referenced with too few arguments. |
| Repair Text: | From Oracle doc: Check the function syntax and specify the required number of arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-939 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | too many arguments for function |
| Long Text: | The function was referenced with too many arguments. |
| Repair Text: | From Oracle doc: Check the function syntax and specify only the required number of arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-940 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid ALTER command |
| Long Text: | An invalid ALTER option was specified. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-941 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing cluster name |
| Long Text: | The cluster name was either missing or invalid. |
| Repair Text: | From Oracle doc: Specify a valid cluster name. A valid cluster name must start with a letter, be less than or equal to 30 characters, and contain only alphanumeric characters or the special characters $, _, and #. It may not be a reserved word. The name must be specified immediately following the keywords CREATE CLUSTER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-942 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table or view does not exist |
| Long Text: | The table or view entered does not exist, a synonym that is not allowed here was used, or a view was referenced where a table is required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access does not exist in the database, or the application does not have access to it. |
| Repair Text: | From Oracle doc: Check each of the following: the spelling of the table or view name. that a view is not specified where a table is required. that an existing table or view name exists. Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table. Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-943 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cluster does not exist |
| Long Text: | The current user owns no cluster by the specified name. |
| Repair Text: | From Oracle doc: Specify a valid cluster name following the keyword CLUSTER, then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-944 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient number of clustered columns |
| Long Text: | An attempt was made to create a table with fewer cluster columns than were specified in the CREATE CLUSTER statement. The CLUSTER clause of a CREATE TABLE statement must specify all cluster columns that were defined when the cluster was created. |
| Repair Text: | From Oracle doc: Specify all cluster columns in the CREATE TABLE statement, then retry it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-945 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified clustered column does not exist |
| Long Text: | A column specified in the cluster clause of a CREATE TABLE statement is not a column in this table. |
| Repair Text: | From Oracle doc: Re-execute the statement, using the names of columns defined for the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-946 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing TO keyword |
| Long Text: | A GRANT statement was specified without the keyword TO, or an invalid form of the GRANT command was entered. |
| Repair Text: | From Oracle doc: Check the syntax for the GRANT command, insert the keyword TO where required, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-947 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not enough values |
| Long Text: | This error occurs when a SQL statement requires two sets of values equal in number, but the second set contains fewer items than the first set. This can occur in a WHERE or HAVING clause in which a nested SELECT returns too few columns as in: WHERE (A,B) IN (SELECT C FROM ...)
INSERT INTO EMP(EMPNO,ENAME) VALUES('JONES') |
| Repair Text: | From Oracle doc: Check the number of items in each set and change the SQL statement to make them equal. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-948 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER CLUSTER statement no longer supported |
| Long Text: | The ALTER CLUSTER statement has been withdrawn. |
| Repair Text: | From Oracle doc: To add data to a cluster from an existing table, use the following series of SQL statements: CREATE TABLE newtable SELECT * FROM oldtable CLUSTER clustername; |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-949 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal reference to remote database |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-950 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid DROP option |
| Long Text: | A DROP command was not followed by a valid DROP option, such as CLUSTER, DATABASE LINK, INDEX, ROLLBACK SEGMENT, SEQUENCE, SYNONYM, TABLE, TABLESPACE, or VIEW. |
| Repair Text: | From Oracle doc: Check the command syntax, specify a valid DROP option, then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-951 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cluster not empty |
| Long Text: | A DROP CLUSTER statement specified a cluster that is not empty. A cluster may not be dropped if it contains any tables, unless the optional INCLUDING TABLES clause is specified. Tables may also be removed from a cluster by using the DROP TABLE command. |
| Repair Text: | From Oracle doc: Either specify the INCLUDING TABLES clause in the DROP CLUSTER statement or remove all tables from the cluster with the DROP TABLE command before issuing the DROP CLUSTER command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-952 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing GROUP keyword |
| Long Text: | Groups are not currently implemented. |
| Repair Text: | From Oracle doc: No user action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-953 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid index name |
| Long Text: | In a CREATE INDEX, DROP INDEX, or VALIDATE INDEX statement, the index name was missing or invalid. |
| Repair Text: | From Oracle doc: Specify a valid index name after the keyword INDEX. To drop or validate an existing index, check the name by querying the data dictionary. To create a new index, check the syntax before retrying. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-954 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing IDENTIFIED keyword |
| Long Text: | A GRANT CONNECT statement was issued without the keyword IDENTIFIED. |
| Repair Text: | From Oracle doc: Check the syntax and insert the keyword IDENTIFIED after the last username. The format is GRANT CONNECT TO user-list IDENTIFIED BY password-list; |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-955 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name is already used by an existing object |
| Long Text: | An attempt was made to create a database object (such as a table, view, cluster, index, or synonym) that already exists. A user's database objects must have distinct names. |
| Repair Text: | From Oracle doc: Enter a unique name for the database object or modify or drop the existing object so it can be reused. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-956 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing or invalid auditing option |
| Long Text: | An AUDIT or NOAUDIT command was not followed by a valid option or the keyword ALL. For example, when AUDITing tables an option such as ALTER, AUDIT, COMMENT, DELETE, GRANT, INDEX, INSERT, LOCK, RENAME, SELECT, or UPDATE must be specified. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-957 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate column name |
| Long Text: | A column name was specified twice in a CREATE or INSERT statement. Column names must be unique within a table, view, or cluster. |
| Repair Text: | From Oracle doc: In a CREATE statement, change one of the column names to a new, unique column name. In an INSERT statement, remove one of the duplicate names. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-958 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing CHECK keyword |
| Long Text: | The keyword CHECK should follow the keyword WITH in the WITH OPTION clause of the CREATE VIEW statement. |
| Repair Text: | From Oracle doc: Check the statement syntax and insert the keyword CHECK where required. Then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-959 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' does not exist |
| Long Text: | A statement specified the name of a tablespace that does not exist. |
| Repair Text: | From Oracle doc: Enter the name of an existing tablespace. For a list of tablespace names, query the data dictionary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-960 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ambiguous column naming in select list |
| Long Text: | A column name in the order-by list matches more than one select list columns. |
| Repair Text: | From Oracle doc: Remove duplicate column naming in select list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-961 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad datetime/interval value |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-962 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many group-by / order-by expressions |
| Long Text: | The group-by or order-by column list contain more than 1000 expressions. |
| Repair Text: | From Oracle doc: Use no more than 1000 expressions in the group-by or order-by list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-963 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported interval type |
| Long Text: | An unsupported interval type was encountered. |
| Repair Text: | From Oracle doc: Use a valid interval type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-964 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table name not in FROM list |
| Long Text: | A table specified in a query's SELECT list is not named in the FROM clause list. |
| Repair Text: | From Oracle doc: Check spelling of the table names, check that each table name in the SELECT list matches a table name in the FROM list, and then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-965 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column aliases not allowed for '*' |
| Long Text: | An alias was used with the return-all-columns function (*) in the SELECT list. For example: SELECT * COL_ALIAS FROM EMP; |
| Repair Text: | From Oracle doc: Either specify individual columns or do not specify an alias with a "*". |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-966 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing TABLE keyword |
| Long Text: | A LOCK statement was specified and the keyword TABLE was missing, misspelled, or misplaced. A LOCK statement must begin with LOCK TABLE tablename. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-967 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing WHERE keyword |
| Long Text: | The keyword WHERE in a SELECT statement was missing, misspelled, or misplaced. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-968 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing INDEX keyword |
| Long Text: | The keyword INDEX in a CREATE UNIQUE INDEX or VALIDATE INDEX statement was missing, misspelled, or misplaced. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-969 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing ON keyword |
| Long Text: | The keyword ON in a GRANT, REVOKE, or CREATE INDEX statement was missing, misspelled, or misplaced. |
| Repair Text: | From Oracle doc: Check syntax and spelling, and use the keyword ON where required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-970 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing WITH keyword |
| Long Text: | The keyword START was specified without the keyword WITH. Both keywords are necessary if a START WITH clause is desired in a tree-structured query. |
| Repair Text: | From Oracle doc: Change the keyword START to the keywords START WITH. Then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-971 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing SET keyword |
| Long Text: | The keyword SET in an UPDATE statement is missing, misspelled, or misplaced. |
| Repair Text: | From Oracle doc: Check syntax and spelling, and use the keyword SET after the name of the table to be updated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-972 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | identifier is too long |
| Long Text: | The name of a schema object exceeds 30 characters. Schema objects are tables, clusters, views, indexes, synonyms, tablespaces, and usernames. |
| Repair Text: | From Oracle doc: Shorten the name to 30 characters or less. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-973 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid row count estimate |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-974 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid PCTFREE value (percentage) |
| Long Text: | The percentage of free space specified in a CREATE INDEX statement is not between 0 and 100. A PCTFREE value of 0 means the entire block is available. The value 100 is not useful because it means that no data may be inserted. The default is 10. |
| Repair Text: | From Oracle doc: Specify a PCTFREE value between 0 and 100. Then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-975 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | date + date not allowed |
| Long Text: | An attempt was made to add two date fields together. Dates may be added only to numeric fields, not to other dates. |
| Repair Text: | From Oracle doc: Use the Oracle function TO_NUMBER to convert one of the date fields to a numeric field before adding it to the other date field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-976 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | LEVEL, PRIOR, or ROWNUM not allowed here |
| Long Text: | The use of the PRIOR clause, the pseudo-column LEVEL, or ROWNUM is incorrect in this context. |
| Repair Text: | From Oracle doc: Check the syntax for the SQL statement. Then remove or relocate the keyword PRIOR, LEVEL, or ROWNUM. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-977 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate auditing option |
| Long Text: | An AUDIT or NOAUDIT statement specified the same option more than once. |
| Repair Text: | From Oracle doc: Either specify ALL without other auditing options or remove the duplicate auditing specifications. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-978 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | nested group function without GROUP BY |
| Long Text: | A group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used within another group function, as in MAX(COUNT(*)), without a corresponding GROUP BY clause. |
| Repair Text: | From Oracle doc: Either add a GROUP BY clause or remove the extra level of nesting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-979 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a GROUP BY expression |
| Long Text: | The GROUP BY clause does not contain all the expressions in the SELECT clause. SELECT expressions that are not included in a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, must be listed in the GROUP BY clause. |
| Repair Text: | From Oracle doc: Include in the GROUP BY clause all SELECT expressions that are not group function arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-980 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | synonym translation is no longer valid |
| Long Text: | The synonym used is based on a table, view, or synonym that no longer exists. |
| Repair Text: | From Oracle doc: Replace the synonym with the name of the object it references or re-create the synonym so that it refers to a valid table, view, or synonym. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-981 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot mix table and system auditing options |
| Long Text: | Both table-wide and system-wide options were specified within a single AUDIT statement. |
| Repair Text: | From Oracle doc: Check the AUDIT command syntax. Then retry one or more AUDIT statements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-982 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing plus sign |
| Long Text: | A left parenthesis appeared in a join condition, but a plus sign (+) did not follow. A left parenthesis in a join condition usually signals an outer-join specification and so a plus sign is expected to follow. To specify an outer join on a column in a join operation, follow the column reference in the join condition with a plus sign (+) enclosed in parentheses. |
| Repair Text: | From Oracle doc: Correct the SQL syntax and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-984 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | column not allowed here |
| Long Text: | A column name was used in an expression where it is not permitted, such as in the VALUES clause of an INSERT statement. |
| Repair Text: | From Oracle doc: Check the syntax of the statement and use column names only where appropriate. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-985 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid program name |
| Long Text: | Probably a syntax error. |
| Repair Text: | From Oracle doc: Correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-986 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing or invalid group name(s) |
| Long Text: | Probably a syntax error. |
| Repair Text: | From Oracle doc: Correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-987 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid username(s) |
| Long Text: | No username was specified in a GRANT statement or one of the specified usernames is invalid. Valid usernames must be specified following the keyword TO in a GRANT statement to define a user. A username must begin with a letter, consist only of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. If it contains other characters, it must be enclosed in double quotation marks. It may not be a reserved word. |
| Repair Text: | From Oracle doc: Specify a valid username, or list of usernames, following the keyword TO in the GRANT statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-988 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid password(s) |
| Long Text: | More usernames than passwords were specified in a GRANT statement. A valid password must be specified for each username listed in the GRANT statement. |
| Repair Text: | From Oracle doc: Enter a valid password for each username. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-989 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many passwords for usernames given |
| Long Text: | More passwords than usernames were specified in a GRANT statement. Only one password may be entered for each username listed in the GRANT statement. |
| Repair Text: | From Oracle doc: Enter an equal number of usernames and passwords. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-990 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid privilege |
| Long Text: | No privileges were specified in a GRANT privilege statement, or one of the specified privileges is invalid. |
| Repair Text: | From Oracle doc: Enter one or more valid privileges such as SELECT, INSERT, DELETE, UPDATE, ALTER, INDEX, REFERENCES, or ALL. More than one privilege may be granted by entering the privileges in a list separated by commas (,) or by specifying the keyword ALL to grant all privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-991 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only MAC privileges may be granted to procedures |
| Long Text: | Object privileges or non-MAC system privileges were granted to the procedure. |
| Repair Text: | From Oracle doc: Only grant MAC privileges using the PROCEDURE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-992 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid format for REVOKE command |
| Long Text: | An invalid form of the REVOKE command was entered. There are two forms of the REVOKE command. The first form is used to revoke a user's database access privileges. The second form is used to revoke a user's object privileges. |
| Repair Text: | From Oracle doc: Check the command syntax and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-993 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing GRANT keyword |
| Long Text: | The keyword WITH was specified at the end of a GRANT statement without the keyword GRANT. To grant privileges to a user and the permission to grant those privileges to another user, you must specify the keywords WITH GRANT OPTION at the end of the GRANT statement. |
| Repair Text: | From Oracle doc: Change the keyword WITH to the keywords WITH GRANT OPTION, then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-994 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing OPTION keyword |
| Long Text: | The keywords WITH GRANT were specified at the end of a GRANT statement without the keyword OPTION. |
| Repair Text: | From Oracle doc: Change the keywords WITH GRANT to the keywords WITH GRANT OPTION. Then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-995 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid synonym identifier |
| Long Text: | In a CREATE or DROP SYNONYM statement, the synonym name was either missing or invalid. |
| Repair Text: | From Oracle doc: Check syntax and spelling. A valid synonym name must be specified immediately following the keyword SYNONYM in both statements. Valid synonym names must begin with a letter, consist of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. They may not be reserved words. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-996 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the concatenate operator is ||, not | |
| Long Text: | A single bar (|) was interpreted as an attempt to specify concatenation, but the concatenation operator is a double bar (||). |
| Repair Text: | From Oracle doc: Enter a double bar (||) for concatenation or remove the single bar (|) if concatenation was not intended. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-997 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal use of LONG datatype |
| Long Text: | A value of datatype LONG was used in a function or in a DISTINCT, WHERE, CONNECT BY, GROUP BY, or ORDER BY clause. A LONG value can only be used in a SELECT clause. |
| Repair Text: | From Oracle doc: Remove the LONG value from the function or clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-998 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must name this expression with a column alias |
| Long Text: | An expression or function was used in a CREATE VIEW statement, but no corresponding column name was specified. When expressions or functions are used in a view, all column names for the view must be explicitly specified in the CREATE VIEW statement. |
| Repair Text: | From Oracle doc: Enter a column name for each column in the view in parentheses after the view name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-999 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid view name |
| Long Text: | In a CREATE VIEW statement, the view name was missing or invalid. |
| Repair Text: | From Oracle doc: Enter a valid view name following CREATE VIEW. Valid view names must begin with a letter, consist of only alphanumeric characters and the special characters $, _, and #, be less than or equal to 30 characters, and may not be reserved words. If the view name contains other characters, it must be enclosed in double quotation marks. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum open cursors exceeded |
| Long Text: | A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user. |
| Repair Text: | From Oracle doc: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid cursor |
| Long Text: | Either a host language program call specified an invalid cursor or the values of the AREASIZE and MAXOPENCURSORS options in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF. |
| Repair Text: | From Oracle doc: Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the AREASIZE and MAXOPENCURSORS options before precompiling. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fetch out of sequence |
| Long Text: | In a host language program, a FETCH call was issued out of sequence. A successful parse-and-execute call must be issued before a fetch. This can occur if an attempt was made to FETCH from an active set after all records have been fetched. This may be caused by fetching from a SELECT FOR UPDATE cursor after a commit. A PL/SQL cursor loop implicitly does fetches and may also cause this error. |
| Repair Text: | From Oracle doc: Parse and execute a SQL statement before attempting to fetch the data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no statement parsed |
| Long Text: | A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE, and FETCH. |
| Repair Text: | From Oracle doc: Do the SQL call, for example, OSQL, to pass the required SQL statement before referencing the cursor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | default username feature not supported; logon denied |
| Long Text: | An attempt was made to use automatic logon on a system not supporting this feature. |
| Repair Text: | From Oracle doc: Provide the complete username and password to log on to Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null password given; logon denied |
| Long Text: | An invalid password was given when logging on. |
| Repair Text: | From Oracle doc: Provide a valid password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bind variable does not exist |
| Long Text: | A program issued a BIND call for a variable not listed in the associated SQL statement. Only those variables prefixed by either a colon (:) or ampersand (&) in the SQL statement may be referenced in a BIND call, OBIND or OBINDN. This error may also be caused by a mismatch between a Precompiler program and the related library, SQLLIB. |
| Repair Text: | From Oracle doc: Modify the BIND call to reference one of the substitute variables specified in the associated SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | variable not in select list |
| Long Text: | A reference was made to a variable not listed in the SELECT clause. In OCI, this can occur if the number passed for the position parameter is less than one or greater than the number of variables in the SELECT clause in any of the following calls: DESCRIBE, NAME, or DEFINE. In SQL*Forms or SQL*Report, specifying more variables in an INTO clause than in the SELECT clause also causes this error. |
| Repair Text: | From Oracle doc: Determine which of the problems listed caused the problem and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not all variables bound |
| Long Text: | A SQL statement containing substitution variables was executed without all variables bound. All substitution variables must have a substituted value before the SQL statement is executed. |
| Repair Text: | From Oracle doc: In OCI, use an OBIND or OBINDN call to substitute the required values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1009 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing mandatory parameter |
| Long Text: | A host language program call did not pass all required parameters. |
| Repair Text: | From Oracle doc: Check the syntax for the call and enter all required parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid OCI operation |
| Long Text: | One of the following: You attempted an invalid OCI operation. You are using an Oracle client application linked version 7.1, or higher libraries, the environment ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to connect to a version 7.0, or lower, Oracle Server. You are connected to a version 7.1, or higher, Oracle Server, the initialization parameter DBLINK_ENCRYPT_LOGIN is set to TRUE, and you attempted to use a database link pointing to a version 7.0, or lower, Oracle Server. |
| Repair Text: | From Oracle doc: For the above causes: Do not use the invalid OCI operation. If you do not wish to use encrypted connect passwords in your distributed database, set ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect passwords, you must upgrade all Oracle Servers to version 7.1, or higher. If you do not wish to use encrypted database links in your distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links, you must upgrade all Oracle Servers to version 7.1, or higher. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use V7 compatibility mode when talking to V6 server |
| Long Text: | An attempt was made to use Oracle7 compatibility mode when accessing Oracle Version 6. |
| Repair Text: | From Oracle doc: Use V6 SQL language type. You may need to use the SET COMPATIBILITY V6 command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not logged on |
| Long Text: | A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle. This can occur when a user process attempts to access the database after the instance it is connected to terminates, forcing the process to disconnect. |
| Repair Text: | From Oracle doc: Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle calls. When the instance has been restarted, retry the action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1013 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | user requested cancel of current operation |
| Long Text: | The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation. This forces the current operation to end. This is an informational message only. |
| Repair Text: | From Oracle doc: Continue with the next operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1014 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | ORACLE shutdown in progress |
| Long Text: | A user tried to log on to Oracle while an instance shutdown was in progress. Oracle logons are disabled while Oracle is being shut down. |
| Repair Text: | From Oracle doc: Wait until Oracle is brought back up before attempting to log on. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logon called recursively |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | This function can be called only after a fetch |
| Long Text: | The cursor is in an invalid state. |
| Repair Text: | From Oracle doc: Ensure the appropriate OCI/UPI function is called after the fetch and before the offending function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid username/password; logon denied |
| Long Text: | An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password. |
| Repair Text: | From Oracle doc: Enter a valid username and password combination in the correct format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column does not have a LONG datatype |
| Long Text: | An attempt was made to fetch data using the LONG fetch option, but the specified column was not LONG. |
| Repair Text: | From Oracle doc: Re-execute the fetch without the LONG fetch option or create the table with a LONG column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to allocate memory in the user side |
| Long Text: | The user side memory allocator returned an error. |
| Repair Text: | From Oracle doc: Increase the size of the process heap or switch to the old set of calls. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown context state |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid context size specified |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database operation not supported in this configuration |
| Long Text: | The attempted database operation does not conform to the user programming interface (UPI) for the two communicating Oracle servers. |
| Repair Text: | From Oracle doc: You may need to upgrade one or more of your Oracle servers or re-link your user side application with new libraries. Report the problem to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cursor context not found (Invalid cursor number) |
| Long Text: | The cursor number is not a valid open cursor. |
| Repair Text: | From Oracle doc: Make sure that the cursor is open. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid datatype in OCI call |
| Long Text: | An OCI program call specified an invalid datatype. In OCI calls, Oracle datatypes are specified as numbers between 1 and 7. |
| Repair Text: | From Oracle doc: Check the datatype description and enter the correct number for the datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UPI parameter out of range |
| Long Text: | An integer parameter to a UPI function is out of range. |
| Repair Text: | From Oracle doc: This usually indicates an error in a tool built on top of the Oracle DBMS. Report the error to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | multiple buffers of size > 4000 in the bind list |
| Long Text: | More than one long buffer in the bind list. |
| Repair Text: | From Oracle doc: Change the buffer size to be less than 4000 for the bind variable bound to a normal column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bind variables not allowed for data definition operations |
| Long Text: | An attempt was made to use a bind variable in a SQL data definition operation. |
| Repair Text: | From Oracle doc: Such bind variables are not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal two task error |
| Long Text: | Received send long message but do not have the cursor context. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal two task error |
| Long Text: | Received a request to send the long again when there is no long |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SELECT ... INTO variable does not exist |
| Long Text: | The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement. |
| Repair Text: | From Oracle doc: If it is not possible to correct the statement, call Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges |
| Long Text: | An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. When Trusted Oracle is configure in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login. |
| Repair Text: | From Oracle doc: Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no such userid |
| Long Text: | This is an internal error message related to Export/Import. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1033 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | ORACLE initialization or shutdown in progress |
| Long Text: | An attempt was made to log on while Oracle is being started or shut down. |
| Repair Text: | From Oracle doc: Wait a few minutes. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1034 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE not available |
| Long Text: | Oracle was not started. Possible causes include the following: The SGA requires more space than was allocated for it. The operating-system variable pointing to the instance is improperly defined. |
| Repair Text: | From Oracle doc: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE only available to users with RESTRICTED SESSION privilege |
| Long Text: | Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on. |
| Repair Text: | From Oracle doc: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal variable name/number |
| Long Text: | Unable to find bind context on user side. |
| Repair Text: | From Oracle doc: Make sure that the variable being bound is in the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum cursor memory exceeded |
| Long Text: | An attempt was made to process a complex SQL statement which consumed all available memory of the cursor. |
| Repair Text: | From Oracle doc: Simplify the complex SQL statement. Alternatively, you can use the NO_EXPAND hint which prevents the cost-based optimizer from considering OR-expansion for queries having OR conditions or INLISTS in the WHERE clause. Usually, the optimizer considers using OR expansion and uses this method if it decides the cost is lower than not using it. Refer to Oracle8i Designing and Tuning for Performance for information about using hints. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot write database file version %s with ORACLE version %s |
| Long Text: | An attempt was made to write datafile headers in an old format. The new format cannot be used until after the database has been verified as being compatible with this software version. |
| Repair Text: | From Oracle doc: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges on underlying objects of the view |
| Long Text: | An attempt was made to explain plan on other people's view without the necessary privileges on the underlying objects of the view. |
| Repair Text: | From Oracle doc: Get necessary privileges or do not perform the offending operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid character in password; logon denied |
| Long Text: | There are multibyte characters in the password or some characters in the password are not in US7ASCII range. |
| Repair Text: | From Oracle doc: Resubmit the password with valid characters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error. hostdef extension doesn't exist |
| Long Text: | Pointer to HSTDEF extension in HSTDEF is null. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | detaching a session with open cursors not allowed |
| Long Text: | An attempt was made to detach a session which had open cursors. |
| Repair Text: | From Oracle doc: Close all the cursors before detaching the session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user side memory corruption [%s], [%s], [%s], [%s] |
| Long Text: | The application code corrupted some of the user memory used by Oracle. |
| Repair Text: | From Oracle doc: Make sure that the application code is not overwriting memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | size %s of buffer bound to variable %s exceeds maximum %s |
| Long Text: | An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as: (element_size)*(number of elements) |
| Repair Text: | From Oracle doc: Reduce the buffer size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user %s lacks CREATE SESSION privilege; logon denied |
| Long Text: | A connect was attempted to a userid which does not have create session privilege. |
| Repair Text: | From Oracle doc: Grant the user CREATE SESSION privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1046 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot acquire space to extend context area |
| Long Text: | Oracle could not extend the current area any further because the operating system would not supply any more space. A system-specific message should appear following this message. |
| Repair Text: | From Oracle doc: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1047 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The above error occurred in schema=%s, package=%s, procedure=%s |
| Long Text: | This message is displayed after a previous message to provide more specific information. |
| Repair Text: | From Oracle doc: See the cause and action for the previous message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1048 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Couldn't find the specified procedure in the given context |
| Long Text: | The procedure user specified in deferred RPC does not exist. |
| Repair Text: | From Oracle doc: Check to make sure that the procedure exists and is visible to the replication process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1049 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Bind by name is not spupportted in streamed RPC |
| Long Text: | This error occurs when a newer server version requests from an older server version an operation that is not supported. |
| Repair Text: | From Oracle doc: You may need to upgrade one or more of your Oracle servers or relink your user application with new libraries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1050 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot acquire space to open context area |
| Long Text: | Oracle could not open a new context area because the operating system would not supply any more space. A system-specific message should appear following this message. |
| Repair Text: | From Oracle doc: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1051 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | deferred rpc buffer format invalid |
| Long Text: | The deferred RPC data in SYS.DEF$_CALL is corrupted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | required destination LOG_ARCHIVE_DUPLEX_DEST is not specified |
| Long Text: | A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to 2. |
| Repair Text: | From Oracle doc: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to 1. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user storage address cannot be read |
| Long Text: | A bind variable or other user area could not be read by Oracle. |
| Repair Text: | From Oracle doc: Check that binds are done correctly on valid user buffers, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user storage address cannot be written |
| Long Text: | A define, FETCH... INTO or SELECT... INTO, variable or other user area could not be written to by Oracle. |
| Repair Text: | From Oracle doc: Check that INTO variables and indicators are correctly specified. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1057 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or ambiguous block.field reference in user exit |
| Long Text: | The reference to a block.field identifier in a user exit is incorrect or ambiguous, probably because it is misspelled or incomplete. |
| Repair Text: | From Oracle doc: Check syntax and identifier spelling. Then correct the reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1058 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal New Upi interface error |
| Long Text: | Attempt to delete non-existent HSTDEF extension. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1059 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parse expected before a bind or execute |
| Long Text: | The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed. |
| Repair Text: | From Oracle doc: Ensure the statement is parsed before a bind or execute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | array binds or executes not allowed |
| Long Text: | The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor. |
| Repair Text: | From Oracle doc: Bind a single cursor or execute the PL/SQL block once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start up a V8 server using a V7 client application |
| Long Text: | You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server. |
| Repair Text: | From Oracle doc: Use a client application linked with V8 (or higher) libraries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1070 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Using an old version of Oracle for the server |
| Long Text: | An attempt was made to run an older, obsolete Oracle Server. |
| Repair Text: | From Oracle doc: Upgrade the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform operation without starting up ORACLE |
| Long Text: | An attempt was made to perform an operation before Oracle was started. |
| Repair Text: | From Oracle doc: Start Oracle. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1072 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot stop ORACLE; ORACLE not running |
| Long Text: | An attempt was made to stop Oracle, but Oracle was not running. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1073 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | fatal connection error: unrecognized call type |
| Long Text: | An illegal internal operation was attempted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot shut down ORACLE; inside a login session - log off first |
| Long Text: | An attempt was made to shut down Oracle inside a logon session. |
| Repair Text: | From Oracle doc: Log off before shutting down Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1075 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | you are currently logged on |
| Long Text: | An attempt was made to log on while already logged on. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1076 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | multiple logons per process not yet supported |
| Long Text: | Oracle does not support multiple logons per process. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1077 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | background process initialization failure |
| Long Text: | A failure occurred during initialization of the background processes. |
| Repair Text: | From Oracle doc: Refer to the diagnostic information in the accompanying message stack or in the trace file and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure in processing system parameters |
| Long Text: | Failure during processing of initialization parameters during system startup. |
| Repair Text: | From Oracle doc: Further diagnostic information should be in the error stack. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1079 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE database was not properly created, operation aborted |
| Long Text: | There was an error when the database or control file was created. |
| Repair Text: | From Oracle doc: Check what error was signaled when the database was first created or when the control file was re-created. Take appropriate actions to re-create the database or a new control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1080 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in shutting down ORACLE |
| Long Text: | A failure occurred during system shutdown. |
| Repair Text: | From Oracle doc: Refer to the diagnostic information in the accompanying message stack and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1081 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start already-running ORACLE - shut it down first |
| Long Text: | An attempt was made to start Oracle while it was already running. |
| Repair Text: | From Oracle doc: Shut down Oracle first, if you want to restart it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | 'row_locking = always' requires the transaction processing option |
| Long Text: | "row_locking = always" is specified in the INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option. |
| Repair Text: | From Oracle doc: Remove it from INIT.ORA file or set it to "default" or "intent". |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1083 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value of parameter "%s" is inconsistent with that of other servers |
| Long Text: | The value of the given initialization parameter is required to be the same for all servers in the parallel configuration. |
| Repair Text: | From Oracle doc: Change the value in the initialization parameter file to match that of the other control files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid argument in OCI call |
| Long Text: | The failing OCI call contains an argument with an invalid value. |
| Repair Text: | From Oracle doc: Use valid argument values. For more information, see the Oracle Call Interface Programmer's Guide and the appropriate programming language supplement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1085 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | preceding errors in deferred rpc to "%s.%s.%s" |
| Long Text: | Errors were encountered when the named procedure was executed as a deferred remote procedure call. |
| Repair Text: | From Oracle doc: Correct the cause of the preceding errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1086 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | savepoint '%s' never established |
| Long Text: | An attempt was made to roll back to a savepoint that was never established. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1087 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start up ORACLE - currently logged on |
| Long Text: | An attempt was made to start up Oracle by a user who is currently logged on. |
| Repair Text: | From Oracle doc: Log off. Then issue the STARTUP command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1088 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot shut down ORACLE while active processes exist |
| Long Text: | Users are still logged into the instance. |
| Repair Text: | From Oracle doc: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1089 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | immediate shutdown in progress - no operations are permitted |
| Long Text: | The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, terminating any active operations. |
| Repair Text: | From Oracle doc: Wait for the instance to be restarted or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1090 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | shutdown in progress - connection is not permitted |
| Long Text: | The SHUTDOWN command was used to shut down a running Oracle instance, disallowing any connects to Oracle. |
| Repair Text: | From Oracle doc: Wait for the instance to restart or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1091 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure during startup force |
| Long Text: | Unable to destroy the old SGA. |
| Repair Text: | From Oracle doc: Manually remove the old SGA. See your operating system-specific Oracle documentation for instructions. Then retry the STARTUP command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1092 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE instance terminated. Disconnection forced |
| Long Text: | The instance connected to was terminated abnormally, probably due to a SHUTDOWN ABORT. The current process was forced to disconnect from the instance. |
| Repair Text: | From Oracle doc: Contact the database administrator to determine when the instance is restarted. Attempt to reconnect after the instance is running again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1093 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER DATABASE CLOSE only permitted with no sessions connected |
| Long Text: | There is at lease one more session, other than the current one, logged in to the instance. ALTER DATABASE CLOSE is not permitted when other sessions are active. |
| Repair Text: | From Oracle doc: Find the other sessions and disconnect them. Then retry the ALTER DATABASE CLOSE command. Also, issue the SHUTDOWN IMMEDIATE command to force users off the system, or issue the SHUTDOWN ABORT command to shut down the database without waiting for users to be forced off. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1094 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER DATABASE CLOSE in progress. Connections not permitted |
| Long Text: | An attempt was made to connect while the database is being closed with the ALTER DATABASE CLOSE command. |
| Repair Text: | From Oracle doc: Attempt to connect again when the database is open. Contact the database administrator to find out when the database will be open. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1095 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DML statement processed zero rows |
| Long Text: | A DML cursor from the OTEX() call processed 0 rows when executed. |
| Repair Text: | From Oracle doc: Caller can either do a rollback or ignore the message and execute the rest of the cursors in the cursor array. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1096 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | program version (%s) incompatible with instance (%s) |
| Long Text: | The program was linked with a different version of the server than the instance to which it is attempting to connect. |
| Repair Text: | From Oracle doc: Relink the program against the same version of Oracle as the instance or restart (startup force) the database using the program's version of the SERVER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1097 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot shutdown while in a transaction - commit or rollback first |
| Long Text: | An attempt was made to shut down the database while a transaction was in progress. |
| Repair Text: | From Oracle doc: Either commit or rollback the current transaction and then attempt to shut down the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1098 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | program Interface error during Long Insert |
| Long Text: | The application program interface could not insert or update a LONG column because of an internal error when a TTCGETV call fails. For example, a network read error or one of the parameters passed to the call is invalid. |
| Repair Text: | From Oracle doc: Retry the insert or update. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1099 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot mount database in SHARED mode if started in single process mode |
| Long Text: | An attempt was made to mount a database in parallel mode with the initialization parameter SINGLE_PROCESS set to TRUE. |
| Repair Text: | From Oracle doc: Either mount the database in EXCLUSIVE mode or set the initialization parameter SINGLE_PROCESS to FALSE before starting the instance in parallel (shared) mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database already mounted |
| Long Text: | An attempt was made to mount a database with the name of a currently mounted database. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database being created currently mounted by some other instance |
| Long Text: | Some other instance has the database of same name currently mounted and you are trying to create it. |
| Repair Text: | From Oracle doc: Either change the database name or shut down the other instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot mount database in EXCLUSIVE mode |
| Long Text: | Some other instance has the database mounted exclusive or shared. |
| Repair Text: | From Oracle doc: Shut down the other instance or mount in a compatible mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database name '%s' in controlfile is not '%s' |
| Long Text: | The database name in the control file does not match your database name. |
| Repair Text: | From Oracle doc: Either find the correct control file or change your database name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1104 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of controlfiles (%s) does not equal %s |
| Long Text: | The number of control files used by this instance disagrees with the number of control files in an existing instance. |
| Repair Text: | From Oracle doc: Check to make sure that all control files are listed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | mount is incompatible with mounts by other instances |
| Long Text: | An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why. |
| Repair Text: | From Oracle doc: See accompanying errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database must be closed before dismounting |
| Long Text: | An attempt was made to dismount a database before it was closed. |
| Repair Text: | From Oracle doc: Close the database, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database must be mounted for media recovery |
| Long Text: | An attempt to perform media recovery was made but the database is not mounted. |
| Repair Text: | From Oracle doc: Mount the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is in backup or media recovery" |
| Long Text: | Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery. |
| Repair Text: | From Oracle doc: Complete or cancel the media recovery session or backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database not open |
| Long Text: | A command was attempted that requires the database to be open. |
| Repair Text: | From Oracle doc: Open the database and try the command again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file %s: '%s' |
| Long Text: | This message reports the file name involved with other messages. |
| Repair Text: | From Oracle doc: See the associated messages for a description of the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name for data file %s is unknown - rename to correct file |
| Long Text: | The datafile was missing from a CREATE CONTROLFILE command or BACKUP CONTROLFILE RECOVERY was done with a control file that was saved before the file was created. |
| Repair Text: | From Oracle doc: Rename the MISSING file to the name of the real file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | media recovery not started |
| Long Text: | An attempt to continue media recovery is being made but media recovery was not started. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s needs media recovery |
| Long Text: | An attempt was made to open a datafile that is in need of media recovery. |
| Repair Text: | From Oracle doc: First apply media recovery to the datafile identified in the message, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IO error writing block to file %s (block # %s) |
| Long Text: | The device on which the file resides is probably off line. |
| Repair Text: | From Oracle doc: Restore access to the device, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IO error reading block from file %s (block # %s) |
| Long Text: | The device on which the file resides is probably off line. |
| Repair Text: | From Oracle doc: Restore access to the device, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in opening database file %s |
| Long Text: | Usually the file is not accessible. |
| Repair Text: | From Oracle doc: Make sure the datafile is in the expected location and can be accessed properly, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1117 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | adding file '%s' with illegal block size: %s; limit is %s |
| Long Text: | An attempt was made to add a datafile with a block size that is greater than the maximum block size allowed. |
| Repair Text: | From Oracle doc: Retry the operation with a smaller block size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1118 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add any more database files: limit of %s exceeded |
| Long Text: | An attempt to add a datafile failed because the limit for such files had already been reached. |
| Repair Text: | From Oracle doc: If more database space is required, export the database and re-create it with a higher limit for datafiles and perhaps increased file size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1119 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in creating database file '%s' |
| Long Text: | Insufficient space on device. |
| Repair Text: | From Oracle doc: Decrease the size of the requested file or allocate a file on another device with more available space. If a file size was not specified in the statement, then specify a file size smaller than the available space on the device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot remove online database file %s |
| Long Text: | An attempt was made to drop a datafile when it is online. |
| Repair Text: | From Oracle doc: Take file offline before dropping. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot rename database file %s - file is in use or recovery |
| Long Text: | An attempt was made to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered. |
| Repair Text: | From Oracle doc: Close database in all instances and end all recovery sessions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database file %s failed verification check |
| Long Text: | The information in this file is inconsistent with information from the control file. See accompanying message for reason. |
| Repair Text: | From Oracle doc: Make certain that the database files and control files are the correct files for this database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start online backup; media recovery not enabled |
| Long Text: | An attempt to start backup of an online tablespace failed because media recovery is not enabled. |
| Repair Text: | From Oracle doc: Enable media recovery and retry this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot recover data file %s - file is in use or recovery |
| Long Text: | An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is currently doing media recovery on the file. |
| Repair Text: | From Oracle doc: Do not do media recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot disable media recovery - file %s has online backup set |
| Long Text: | An attempt to disable media recovery found that an online backup is still in progress. |
| Repair Text: | From Oracle doc: End the backup of the offending tablespace and retry this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database must be mounted EXCLUSIVE and not open for this operation |
| Long Text: | An operation failed because the database was not mounted in exclusive mode. |
| Repair Text: | From Oracle doc: Shut down Oracle and mount the database in exclusive mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database name '%s' exceeds size limit of %s characters |
| Long Text: | The specified database name is too long. |
| Repair Text: | From Oracle doc: Shorten the database name to eight characters or fewer, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start online backup - file %s is offline |
| Long Text: | An attempt to start an online backup found that one of the files is offline. |
| Repair Text: | From Oracle doc: Bring the offending files online and retry this command or do a cold backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1129 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user's default or temporary tablespace does not exist |
| Long Text: | The user's default or temporary tablespace was dropped. |
| Repair Text: | From Oracle doc: Reassign the default or temporary tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1130 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database file version %s incompatible with ORACLE version %s |
| Long Text: | The named datafile was created under an incompatible version of Oracle, or the file is invalid or non-existent. |
| Repair Text: | From Oracle doc: Shut down and restart the correct version of Oracle or check the references to the datafile and make sure it exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1131 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DB_FILES system parameter value %s exceeds limit of %s |
| Long Text: | The specified value of the initialization parameter DB_FILES is too large. |
| Repair Text: | From Oracle doc: Reduce the value of the DB_FILES parameter and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1132 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | length of database file name '%s' exceeds limit of %s characters |
| Long Text: | The specified datafile name is too long. |
| Repair Text: | From Oracle doc: Shorten the file name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1133 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | length of log file name '%s' exceeds limit of %s characters |
| Long Text: | The specified redo log file name is too long. |
| Repair Text: | From Oracle doc: Shorten the file name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1134 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database mounted exclusive by another instance |
| Long Text: | An attempt to access a database failed because it is mounted in exclusive mode by another instance. |
| Repair Text: | From Oracle doc: Either shut down the other instance or wait for the other instance to either close the database or mount it in parallel mode, before retrying the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1135 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s accessed for DML/query is offline |
| Long Text: | An attempt was made to access a datafile that is offline. |
| Repair Text: | From Oracle doc: Bring the datafile back online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1136 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified size of file %s (%s blocks) is less than original size of %s blocks |
| Long Text: | A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller than the size needed. |
| Repair Text: | From Oracle doc: Create the file with a larger size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1137 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | data file %s is still in the middle of going offline |
| Long Text: | It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline. |
| Repair Text: | From Oracle doc: Wait for the other instance to release the lock on the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1138 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database must either be open in this instance or not at all |
| Long Text: | The requested operation cannot be done when the database is mounted but not open in this instance, and another instance has the database open. |
| Repair Text: | From Oracle doc: Execute the operation in an open instance, open the database in this instance, or close the database in the other instances. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1139 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RESETLOGS option only valid after an incomplete database recovery |
| Long Text: | The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session. |
| Repair Text: | From Oracle doc: Retry the ALTER DATABASE OPEN without specifying RESETLOGS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1140 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | cannot end online backup - all files are offline |
| Long Text: | All the files were found to be offline when attempting to end an online backup. |
| Repair Text: | From Oracle doc: No action required. Online backup does not need to be ended for this tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1141 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error renaming data file %s - new file '%s' not found |
| Long Text: | An attempt to change a datafile's name in the control file failed because no file was found with the new name. |
| Repair Text: | From Oracle doc: Make sure that the datafile has been properly renamed by the operating system and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1142 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | cannot end online backup - none of the files are in backup |
| Long Text: | None of the files were found to be in online backup when attempting to end an online backup. |
| Repair Text: | From Oracle doc: No action required. Online backup does not need to be ended for this tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1143 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot disable media recovery - file %s needs media recovery |
| Long Text: | An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled. |
| Repair Text: | From Oracle doc: Recover the offending file or drop the tablespace it belongs to and retry this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1144 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File size (%s blocks) exceeds maximum of %s blocks |
| Long Text: | Specified file size is larger than maximum allowable size value. |
| Repair Text: | From Oracle doc: Specify a smaller size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1145 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | offline immediate disallowed unless media recovery enabled |
| Long Text: | ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode. |
| Repair Text: | From Oracle doc: Take the tablespace offline as usual or do a shutdown abort before attempting the required operation. It is worthwhile reconsidering the backup strategy for the database. The attempted operations can be done if ARCHIVEREDO LOG mode is enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1146 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start online backup - file %s is already in backup |
| Long Text: | An attempt was made to start an online backup, but an online backup was already started for one of the datafiles. |
| Repair Text: | From Oracle doc: End the first backup before beginning another. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1147 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SYSTEM tablespace file %s is offline |
| Long Text: | A file belonging to the SYSTEM tablespace has been marked offline by the database administrator. The database cannot be started until all SYSTEM tablespace files are online and can be opened. |
| Repair Text: | From Oracle doc: Bring the file online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1148 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not mount database PARALLEL without a lock manager installed |
| Long Text: | An attempt was made to mount the database PARALLEL without the existence of a Lock Manager. |
| Repair Text: | From Oracle doc: Mount the database in EXCLUSIVE mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1149 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot shutdown - file %s has online backup set |
| Long Text: | An attempt to shut down normally found that an online backup is still in progress. |
| Repair Text: | From Oracle doc: End the backup of the offending tablespace and retry this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot prevent writes - file %s has online backup set |
| Long Text: | Tablespace cannot be taken offline or made read-only when online backup is running. Ending the backup entails writing the file header, which this operation, were it permitted, would prevent. |
| Repair Text: | From Oracle doc: End the online backup and then take the tablespace offline or make it read-only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | use media recovery to recover block, restore backup if needed |
| Long Text: | Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. This message is usually accompanied by ORA-01172. |
| Repair Text: | From Oracle doc: There is additional information for ORA-01172. Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, restore the file from a backup and recover it again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s was not restored from a sufficiently old backup |
| Long Text: | An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery. |
| Repair Text: | From Oracle doc: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an incompatible media recovery is active |
| Long Text: | Attempt to start an incompatible media recovery or open resetlogs during media recovery. Media recovery sessions are incompatible if they attempt to recover the same datafile. Incomplete media recovery or open resetlogs is incompatible with any media recovery. |
| Repair Text: | From Oracle doc: Complete or cancel the other media recovery session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1154 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | database busy. Open, close, mount, and dismount not allowed now |
| Long Text: | Some operation is in progress that expects the state of the instance to remain open or mounted. |
| Repair Text: | From Oracle doc: Wait for the operation to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1155 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | the database is being opened, closed, mounted or dismounted |
| Long Text: | The attempted operation will not succeed while the instance is in one of the states mentioned in the message. |
| Repair Text: | From Oracle doc: Wait for the open, close, mount, or dismount to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1156 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | recovery in progress may need access to files |
| Long Text: | Either media or instance recovery is in progress. The recovery may need access to the files that the attempted operation tried to use. |
| Repair Text: | From Oracle doc: Wait for the recovery to complete and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1157 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot identify/lock data file %s - see DBWR trace file |
| Long Text: | The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However, the first instance to open the database will need to access all online data files. The accompanying error from the operating system describes why the file could not be identified. |
| Repair Text: | From Oracle doc: At the operating system level, make the file available to the database. Then either open the database or do an ALTER SYSTEM CHECK DATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1158 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database %s already mounted |
| Long Text: | Another instance has a database by this name mounted. |
| Repair Text: | From Oracle doc: Find which instance is still running. Perhaps you have not lost the control files after all. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1159 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file is not from same database as previous files - wrong database id |
| Long Text: | Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified. |
| Repair Text: | From Oracle doc: Check the list of files provided to the CREATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file is not a %s |
| Long Text: | The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated. |
| Repair Text: | From Oracle doc: Check the mentioned file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database name %s in file header does not match given name of %s |
| Long Text: | The database name given at the command line does not match the database name found in the file header. |
| Repair Text: | From Oracle doc: Chance are good that the database name specified at the command line is incorrect. Resolve the discrepancy, and resubmit the command. If you are attempting to change the database name, be sure to use the SET DATABASE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | block size %s in file header does not match DB_BLOCK_SIZE (%s) |
| Long Text: | CREATE CONTROLFILE discovered that the block size for this file is incompatible with the initialization parameter DB_BLOCK_SIZE used to allocate cache buffers. If not the first file then there are a mixture of block sizes, or the file is corrupt. |
| Repair Text: | From Oracle doc: If this is the first file in the command then correct DB_BLOCK_SIZE to match the file and restart the instance. If not the first file find the correct version of the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SIZE clause indicates %s (blocks), but should match header %s |
| Long Text: | The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header. |
| Repair Text: | From Oracle doc: Specify the correct file name and size (in bytes). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1164 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXLOGFILES may not exceed %s |
| Long Text: | MAXLOGFILES specified on the command line too large. |
| Repair Text: | From Oracle doc: Resubmit the command with a smaller value for MAXLOGFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1165 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXDATAFILES may not exceed %s |
| Long Text: | MAXDATAFILES specified on the command line too large. |
| Repair Text: | From Oracle doc: Resubmit the command with a smaller value for MAXDATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1166 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file number %s is larger than %s (%s) |
| Long Text: | File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES. |
| Repair Text: | From Oracle doc: Increase the maximum specified on the command line. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1167 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two files are the same file/group number or the same file |
| Long Text: | There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file specification. This message will also appear if the same control file appears more than once in the CONTROL_FILES parameter in the INIT.ORA file. If this happens, check for additional error messages. |
| Repair Text: | From Oracle doc: Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate control file, check the CONTROL_FILES parameter in the INIT.ORA file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1168 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | physical block size %s does not match size %s of other members |
| Long Text: | The file is located on a device with a different physical block size than the other members in the group. |
| Repair Text: | From Oracle doc: Use a physical device with matching block size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1169 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DATAFILE number 1 not found. Must be present |
| Long Text: | Datafile number 1 was not specified in a CREATE CONTROLFILE command. |
| Repair Text: | From Oracle doc: Locate datafile number 1 and resubmit the CREATE CONTROLFILE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1170 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file not found '%s' |
| Long Text: | A file specified in the CREATE CONTROLFILE statement was not found. All datafiles and all redo log files, if NORESETLOGS was used, must be accessible by the process that issues the CREATE CONTROLFILE statement. |
| Repair Text: | From Oracle doc: Check the statement for a typing mistake in the file name and check for the existence of all files. Then issue the statement again after correcting the file names. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1171 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s going offline due to error advancing checkpoint |
| Long Text: | The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block. |
| Repair Text: | From Oracle doc: See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1172 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recovery of thread %s stuck at block %s of file %s |
| Long Text: | Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. |
| Repair Text: | From Oracle doc: Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem, then restore the file from a backup and recover it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1173 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data dictionary indicates missing data file from system tablespace |
| Long Text: | One of the following: The database is recovered to a point in time in the future of the control file. A datafile from the system tablespace is omitted from the issued CREATE CONTROLFILE statement. |
| Repair Text: | From Oracle doc: One of the following: Recover the database from a more recent control file. Re-create the control file, ensuring all datafiles are included for the system tablespace in the command line. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1174 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DB_FILES is %s buts needs to be %s to be compatible |
| Long Text: | The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open. |
| Repair Text: | From Oracle doc: Change the value of the DB_FILES parameter to be compatible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1175 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data dictionary has more than the %s files allowed by the instance |
| Long Text: | The data dictionary is found to have more files than that which can be supported by this instance. |
| Repair Text: | From Oracle doc: Shut down the instance and restart with a larger value for DB_FILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1176 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data dictionary has more than the %s files allowed by the controlfie |
| Long Text: | After a CREATE CONTROLFILE, the data dictionary was found to have more datafiles than that supported by the control file. |
| Repair Text: | From Oracle doc: Re-create the control file with a larger value for MAXDATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1177 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file does not match dictionary - probably old incarnation |
| Long Text: | When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile. |
| Repair Text: | From Oracle doc: Do a CREATE CONTROLFILE with the correct file or none at all. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1178 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s created before last CREATE CONTROLFILE, cannot recreate |
| Long Text: | An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that existed at the last CREATE CONTROL file command. The information needed to re-create the file was lost with the control file that existed when the file was added to the database. |
| Repair Text: | From Oracle doc: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1179 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s does not exist |
| Long Text: | During datafile recovery, a file was listed that was not part of the database. |
| Repair Text: | From Oracle doc: Recheck the file name. Remember to use single quotation marks at the SQL*DBA command line. Remember also that the file name is translated in the operating environment of SQL*DBA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1180 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not create datafile 1 |
| Long Text: | An attempt was made to create datafile 1 using ALTER DATABASE CREATE DATAFILE. |
| Repair Text: | From Oracle doc: Recover file from a backup or re-create the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1181 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s created before last RESETLOGS, cannot recreate |
| Long Text: | An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that existed at the last RESETLOGS database open. |
| Repair Text: | From Oracle doc: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1182 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create database file %s - file is in use or recovery |
| Long Text: | An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that is online in an open instance or is being recovered. |
| Repair Text: | From Oracle doc: Close database in all instances and end all recovery sessions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1183 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot mount database in SHARED mode |
| Long Text: | Some other instance has the database mounted exclusive. |
| Repair Text: | From Oracle doc: Shut down the other instance and then mount shared. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1184 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logfile group %s already exists |
| Long Text: | An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is already in use. |
| Repair Text: | From Oracle doc: Specify a different log file number, or let the database choose an unused value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1185 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logfile group number %s is invalid |
| Long Text: | An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is too large. |
| Repair Text: | From Oracle doc: Specify a correct log file number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1186 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s failed verification tests |
| Long Text: | The datafile did not pass the checks to insure it is part of the database. See the accompanying error messages for the reason the verification failed. |
| Repair Text: | From Oracle doc: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1187 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot read from file %s because it failed verification tests |
| Long Text: | The datafile did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified. |
| Repair Text: | From Oracle doc: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1188 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Block size %s in header does not match physical block size %s |
| Long Text: | A log file member given to CREATE CONTROLFILE is on a physical device that has a different block size than the device originally used to create the log. |
| Repair Text: | From Oracle doc: Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROLFILE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1189 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file is from a different RESETLOGS than previous files |
| Long Text: | In a CREATE CONTROLFILE command, either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS. |
| Repair Text: | From Oracle doc: If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consistent with the rest of the datafiles and resubmit the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1190 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile or data file %s is from before the last RESETLOGS |
| Long Text: | An attempt was made to use a datafile when the log reset information in the file does not match the control file. Either the datafile or the control file is a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS. |
| Repair Text: | From Oracle doc: Restore file from a more recent backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1191 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is already offline - cannot do a normal offline |
| Long Text: | When attempting to do a normal tablespace offline, it was discovered that one of the files in the tablespace was already offline. |
| Repair Text: | From Oracle doc: Either bring the datafile online first, or use another tablespace offline option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1192 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must have at least one enabled thread |
| Long Text: | At least two redo log files from at least one thread must be specified in the CREATE CONTROLFILE command line. |
| Repair Text: | From Oracle doc: Find the missing redo log files and retry the command with the newly found redo log files included in the command line. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1193 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is not the same file seen at start of recovery |
| Long Text: | A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery. |
| Repair Text: | From Oracle doc: Ensure the correct file is available, and then retry recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1194 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s needs more recovery to be consistent |
| Long Text: | An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery. |
| Repair Text: | From Oracle doc: Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1195 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | online backup of file %s needs more recovery to be consistent |
| Long Text: | An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file is an online backup which must be recovered to the time the backup ended. |
| Repair Text: | From Oracle doc: Either apply more logs until the file is consistent or restore the database files from an older backup and repeat recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1196 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is inconsistent due to a failed media recovery session |
| Long Text: | The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file. |
| Repair Text: | From Oracle doc: Either apply more logs until the file is consistent or restore the backup again and repeat recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1197 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s only contains one log |
| Long Text: | During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs. |
| Repair Text: | From Oracle doc: Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1198 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must specify size for log file if RESETLOGS |
| Long Text: | File sizes must be given for all log files if doing a CREATE CONTROLFILE with the RESETLOGS option. |
| Repair Text: | From Oracle doc: Resubmit the command with the appropriate log file size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1199 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is not in online backup mode |
| Long Text: | An attempt was made to end an online backup for a file that is not in online backup. |
| Repair Text: | From Oracle doc: Do not enter command since it is not needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | actual file size of %s is smaller than correct size of %s blocks |
| Long Text: | The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated. Maybe it is the result of a half completed copy. |
| Repair Text: | From Oracle doc: Restore a good copy of the datafile and do recovery as needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s header failed to write correctly |
| Long Text: | An I/O error was reported for the file header. The error was trapped and a second attempt will be made. |
| Repair Text: | From Oracle doc: The file probably will require recovery. Further error messages will indicate what is needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong incarnation of this file - wrong creation time |
| Long Text: | The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped. |
| Repair Text: | From Oracle doc: Restore a current copy of the datafile and do recovery as needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong incarnation of this file - wrong creation SCN |
| Long Text: | The creation SCN in the file header is not the same as the creation SCN in the control file. This is probably a copy of a file that was dropped. |
| Repair Text: | From Oracle doc: Restore a current copy of the datafile and do recovery as needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file number is %s rather than %s - wrong file |
| Long Text: | The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database. |
| Repair Text: | From Oracle doc: Restore a copy of the correct datafile and do recovery as needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a data file - type number in header is %s |
| Long Text: | The file type in the header is not correct for a datafile. This is probably a log file or control file. If the type is not a small non-zero positive number then the header is corrupted. |
| Repair Text: | From Oracle doc: Restore a copy of the correct datafile and do recovery as needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file is not part of this database - wrong database id |
| Long Text: | The database ID in the file header does not match the database ID in the control file. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected. |
| Repair Text: | From Oracle doc: Restore a copy of the correct datafile and do recovery as needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file is more recent than controlfile - old controlfile |
| Long Text: | The control file change sequence number in the datafile is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough. |
| Repair Text: | From Oracle doc: Use the current control file or do BACKUP CONTROLFILE RECOVERY to make the control file current. Be sure to follow all restrictions on doing a BACKUP CONTROLFILE RECOVERY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file is an old version - not accessing current version |
| Long Text: | The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use. |
| Repair Text: | From Oracle doc: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file is from before the last RESETLOGS |
| Long Text: | The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use. |
| Repair Text: | From Oracle doc: Make the correct file available to the database. Then, either open the database or execute ALTER SYSTEM CHECK DATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file header is media corrupt |
| Long Text: | The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistency of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database. |
| Repair Text: | From Oracle doc: Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle7 data file is not from migration to Oracle8 |
| Long Text: | The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8. |
| Repair Text: | From Oracle doc: Have operating system make correct datafile available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXLOGMEMBERS may not exceed %s |
| Long Text: | MAXLOGMEMBERS specified on the command line too large. |
| Repair Text: | From Oracle doc: Resubmit the command with a smaller value for MAXLOGMEMBERS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXINSTANCES may not exceed %s |
| Long Text: | MAXINSTANCES specified on the command line too large. |
| Repair Text: | From Oracle doc: Resubmit the command with a smaller value for MAXINSTANCES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXLOGHISTORY may not exceed %s |
| Long Text: | MAXLOGHISTORY specified on the command line too large. |
| Repair Text: | From Oracle doc: Resubmit the command with a smaller value for MAXLOGHISTORY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enabled thread %s is missing after CREATE CONTROLFILE |
| Long Text: | A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database. |
| Repair Text: | From Oracle doc: Reissue the CREATE CONTROLFILE statement, including all enabled threads. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s is expected to be disabled after CREATE CONTROLFILE |
| Long Text: | A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread). |
| Repair Text: | From Oracle doc: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be re-created after the database is open. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logfile member belongs to a different logfile group |
| Long Text: | A member of a multiple-member log file group specified in a CREATE CONTROLFILE is not part of the same group as previous members. |
| Repair Text: | From Oracle doc: Group together the correct members for the CREATE CONTROLFILE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logfile member is not from the same point-in-time |
| Long Text: | A member of a multiple-member log file group is from a different point in time. One of the members specified may be an older (backup) copy of the log. |
| Repair Text: | From Oracle doc: Find the correct version of the log, or leave it out of the CREATE CONTROLFILE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database not open: queries allowed on fixed tables/views only |
| Long Text: | A query was issued against an object not recognized as a fixed table or fixed view before the database has been opened. |
| Repair Text: | From Oracle doc: Re-phrase the query to include only fixed objects, or open the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1220 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file based sort illegal before database is open |
| Long Text: | A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open. |
| Repair Text: | From Oracle doc: Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1221 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file %s is not the same file to a background process |
| Long Text: | When the database writer opens the datafile, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all. |
| Repair Text: | From Oracle doc: Look in the DBWR trace file for the error it received when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1222 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXINSTANCES of %s requires MAXLOGFILES be at least %s, not %s |
| Long Text: | An attempt was made to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs. |
| Repair Text: | From Oracle doc: Either reduce the MAXINSTANCES argument or increase the value of MAXLOGFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1223 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RESETLOGS must be specified to set a new database name |
| Long Text: | The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS. |
| Repair Text: | From Oracle doc: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1224 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | group number in header %s does not match GROUP %s |
| Long Text: | Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong. |
| Repair Text: | From Oracle doc: Omit the GROUP option or give the correct one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1225 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread number %s is greater than MAXINSTANCES %s |
| Long Text: | The log is for a thread greater than the MAXINSTANCES argument. |
| Repair Text: | From Oracle doc: Increase the value for MAXINSTANCES and resubmit the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1226 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file header of log member is inconsistent with other members |
| Long Text: | The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log. |
| Repair Text: | From Oracle doc: Find the correct log member or omit this member from the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1227 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s is inconsistent with other logs |
| Long Text: | The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistency. All log files listed in the command must be the current versions of the online logs. |
| Repair Text: | From Oracle doc: Find the correct online logs or use the RESETLOGS option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1228 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SET DATABASE option required to install seed database |
| Long Text: | The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database. |
| Repair Text: | From Oracle doc: Resubmit command with the SET DATABASE and RESETLOGS options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1229 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file %s is inconsistent with logs |
| Long Text: | The datafile in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs. |
| Repair Text: | From Oracle doc: Find the correct online logs or use the RESETLOGS option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot make read only - file %s is offline |
| Long Text: | An attempt to make a tablespace read only found that one of its files is offline. |
| Repair Text: | From Oracle doc: Bring the file online and retry this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot make read write - file %s is offline |
| Long Text: | An attempt to make a tablespace read write found that one of its files is offline. |
| Repair Text: | From Oracle doc: Bring the file online and retry this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start online backup - file %s is read only |
| Long Text: | An attempt to start an online backup found that one of the files is marked read only. Read-only files do not need to be set into online backup mode. |
| Repair Text: | From Oracle doc: Make the backup without the begin backup command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is read only - cannot recover using backup controlfile |
| Long Text: | An attempt to do media recovery using a backup control file found that one of the files is marked read only. Read-only files do not normally need to be recovered, but recovery with a backup control file must recover all online files. |
| Repair Text: | From Oracle doc: If the file really is read only, take it offline before the recovery, and bring the read-only tablespace online after the database is open. If the file does need recovery use a control file from the time the file was read-write. If the correct control file is not available, use CREATE CONTROLFILE to make one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot end backup of file %s - file is in use or recovery |
| Long Text: | An attempt was made to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online. |
| Repair Text: | From Oracle doc: If there is an instance with the database open then the backup can be ended there by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | END BACKUP failed for %s file(s) and succeeded for %s |
| Long Text: | One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded. |
| Repair Text: | From Oracle doc: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1236 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error %s occurred during initialization of file header access |
| Long Text: | The indicated error occurred while doing initialization processing of file headers. |
| Repair Text: | From Oracle doc: The error indicated should be corrected. An attempt is made to recover from this error by using a slower access algorithm. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1237 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot extend datafile %s |
| Long Text: | An operating system error occurred during the resize. |
| Repair Text: | From Oracle doc: Fix the cause of the operating system error and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1238 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot shrink datafile %s |
| Long Text: | An operating system error occurred during the resize. |
| Repair Text: | From Oracle doc: The error is ignored, operation continues normally. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1239 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database must be in ARCHIVELOG mode to use external cache |
| Long Text: | An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this cannot be allowed. |
| Repair Text: | From Oracle doc: Change database to be in ARCHIVELOG mode or do not use an external cache. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1240 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many data files to add in one command |
| Long Text: | The command specifies adding more datafiles than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large. |
| Repair Text: | From Oracle doc: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1241 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an external cache has died |
| Long Text: | The external cache may have been restarted. |
| Repair Text: | From Oracle doc: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You may also restart all instances to make sure they access all datafiles through consistent external caches. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1242 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file suffered media failure: database in NOARCHIVELOG mode |
| Long Text: | The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure. |
| Repair Text: | From Oracle doc: Restore accessibility to the file mentioned in the error stack and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1243 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system tablespace file suffered media failure |
| Long Text: | A system tablespace file was detected as inaccessible due to media failure. |
| Repair Text: | From Oracle doc: Restore accessibility to the file mentioned in the error stack and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1244 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unnamed datafile(s) added to controlfile by media recovery |
| Long Text: | Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files. |
| Repair Text: | From Oracle doc: Rename the files to valid file names and resume recovery. If necessary the command ALTER DATABASE CREATE DATAFILE may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered then take it offline with the FOR DROP option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1245 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | offline file %s will be lost if RESETLOGS is done |
| Long Text: | An attempt was made to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option. |
| Repair Text: | From Oracle doc: Either bring the file online and recover it, or take it offline with the FOR DROP option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1246 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recovering files through TSPITR of tablespace %s |
| Long Text: | The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery. |
| Repair Text: | From Oracle doc: Restore more recent backups and recover them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1247 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database recovery through TSPITR of tablespace %s |
| Long Text: | Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done. |
| Repair Text: | From Oracle doc: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1248 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s was created in the future of incomplete recovery |
| Long Text: | An attempt was made to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed. |
| Repair Text: | From Oracle doc: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1249 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archiving not allowed in a clone database |
| Long Text: | An attempt was made to archive an online redo log or enable archiving for a clone database. |
| Repair Text: | From Oracle doc: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed, then re-create the database not as a clone. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error %s occurred during termination of file header access |
| Long Text: | The indicated error occurred while terminating the processing of file headers. The error was other than a write error. |
| Repair Text: | From Oracle doc: The indicated error should be corrected. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unknown File Header Version read for file number %s |
| Long Text: | Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file. |
| Repair Text: | From Oracle doc: Have the operating system make the correct file available to the database, or recover the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1252 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot prevent writes - file %s in recovery manager backup |
| Long Text: | An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read only, then the file header cannot be updated when the backup is complete. |
| Repair Text: | From Oracle doc: Wait for the Recovery Manager backup to complete and retry this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1253 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot start online backup - file %s in recovery manager backup |
| Long Text: | The specified file is being backed up by Recovery Manager. |
| Repair Text: | From Oracle doc: Wait for the Recovery Manager proxy backup to complete before starting another backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1254 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot end online backup - file %s in recovery manager backup |
| Long Text: | The specified file is being backed up by Recovery Manager. |
| Repair Text: | From Oracle doc: Wait for the Recovery Manager proxy backup to complete. Recovery Manager backup mode cannot be initiated or terminated manually. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1255 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot shutdown - file %s in recovery manager backup |
| Long Text: | An attempt to shut down normally found that a Recovery Manager backup is still in progress. |
| Repair Text: | From Oracle doc: Wait for the Recovery Manager proxy backup to complete and retry this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1280 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Fatal LogMiner Error. |
| Long Text: | On of the following: One or more input parameters in the DBMS_LOGMNR.START_LOGMNR() procedure may be invalid. The start or the end SCN may not be available in the log files selected. The dictionary file specified may be from a different database than the one that generated the log files. LogMiner may have encountered an internal error from which it cannot recover. |
| Repair Text: | From Oracle doc: Check to see whether the input parameters are valid. The V$LOGMNR_LOG view can be queried to see the SCN ranges that are valid for the set of log files specified, and the DB_ID of the database that generated the log files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SCN range specified in dbms_logmnr.start_logmnr() is invalid |
| Long Text: | StartSCN may be greater than EndSCN, or the SCN specified may be invalid. |
| Repair Text: | From Oracle doc: Specify a valid SCN range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1282 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | date range specified in dbms_logmnr.start_logmnr() is invalid |
| Long Text: | The specified Date value is invalid for the log file. |
| Repair Text: | From Oracle doc: Specify a valid date range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1283 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Options specified is invalid |
| Long Text: | The specified Options is invalid for the procedure. |
| Repair Text: | From Oracle doc: Specify valid Options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1284 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s cannot be opened |
| Long Text: | The specified file cannot be opened. |
| Repair Text: | From Oracle doc: Check to make sure the file or directory exists and is accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1285 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error reading file %s |
| Long Text: | The file or directory may not exist or is inaccessible. |
| Repair Text: | From Oracle doc: Specify valid file or directory. Make sure that file and directory are accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1286 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add file %s due to DB_ID mismatch |
| Long Text: | The log file is produced by a different database than other log files already added to the list. |
| Repair Text: | From Oracle doc: Specify a log file produced by the same database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1287 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Reset SCN for file %s does not match that of other logfiles specified for this LogMiner session |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1288 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Reset Count for file %s does not match that of other logfiles specified for this LogMiner session |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1289 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add duplicate logfile %s |
| Long Text: | The log file specified has already been added to the list of log files. |
| Repair Text: | From Oracle doc: Specify a different log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot remove unlisted logfile %s |
| Long Text: | The user attempted to remove a log file that is not present in the list. |
| Repair Text: | From Oracle doc: Specify a valid log file in the DBMS_LOGMNR.ADD_LOGFILE() procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1291 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing logfile |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1292 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no log file has been specified for the current LogMiner session |
| Long Text: | No log file has been specified for the LogMiner session. |
| Repair Text: | From Oracle doc: Specify at least one log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1293 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | time or SCN range not fully contained in the listed logfiles |
| Long Text: | The input date/SCN range is not fully contained within the log files specified for the session. |
| Repair Text: | From Oracle doc: Select out of V$LOGMNR_LOGS view to check the date or SCN range covered by the log files specified for the LogMiner session, and reissue the START_LOGMNR() procedure with appropriate date or SCN range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1294 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred while processing information in dictionary file %s, possible corruption |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1295 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBID mismatch between dictionary %s and logfiles |
| Long Text: | The dictionary file is produced by a database that is different from that produced the log files. |
| Repair Text: | From Oracle doc: Specify a compatible dictionary file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1296 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | character set mismatch between dictionary %s and logfiles |
| Long Text: | The character set of the database that produced the dictionary file is different from the character set of the database that produced the log files. |
| Repair Text: | From Oracle doc: Specify a dictionary file with the same character set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1297 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | redo version mismatch between dictionary %s and logfiles |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1298 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LowSCN mismatch between dictionary %s and the earliest logfile |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1299 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ResetSCN mismatch between dictionary %s and the earliest logfile |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enabled thread bit vector mismatch between dictionary %s and the earliest logfile |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dbms_logmnr.USE_COLMAP can only be used with a valid dictionary |
| Long Text: | DBMS_LOGMNR.USE_COLMAP can only be used with a valid dictionary. |
| Repair Text: | From Oracle doc: Specify the dictionary file in DBMS_LOGMNR.START_LOGMNR(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in logmnr.opt file |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | schema %s, specified in logmnr.opt file, does not exist |
| Long Text: | The schema specified does not exist. |
| Repair Text: | From Oracle doc: Specify a correct schema or a compatible dictionary file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table %s, schema %s, specified in logmnr.opt file, does not exist |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column %s, specified in logmnr.opt file, does not exist in table %s, schema %s |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents |
| Long Text: | A select was issued from V$LOGMNR_CONTENTS without first invoking the DBMS_LOGMNR.START_LOGMNR() procedure. |
| Repair Text: | From Oracle doc: Invoke the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1307 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no LogMiner session is currently active |
| Long Text: | A select was issued from V$LOGMNR_CONTENTS without first invoking the DBMS_LOGMNR.START_LOGMNR() procedure. Otherwise, DBMS_LOGMNR.END_LOGMNR() was called without a prior call to DBMS_LOGMNR.START_LOGMNR() or DBMS_LOGMNR.ADD_LOGFILE() |
| Repair Text: | From Oracle doc: Invoke the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | primary key or mandatory (NOT NULL) column is missing or NULL during insert |
| Long Text: | When inserting or updating rows, a value for a column defined as NOT NULL was not specified. |
| Repair Text: | From Oracle doc: Specify a value for each NOT NULL column or modify the table definition to allow NULL values in columns now defined as NOT NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inserted value too large for column |
| Long Text: | The value entered is larger than the maximum width defined for the column. |
| Repair Text: | From Oracle doc: Enter a value smaller than the column width or use the MODIFY option with ALTER TABLE to expand the column width. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | view WITH CHECK OPTION where-clause violation |
| Long Text: | An INSERT or UPDATE statement was attempted on a view created with the CHECK OPTION. This would have resulted in the creation of a row that would not satisfy the view's WHERE clause. |
| Repair Text: | From Oracle doc: Examine the view's WHERE clause in the dictionary table VIEWS. If the current view does not have the CHECK OPTION, then its FROM clause must reference a second view that is defined using the CHECK OPTION. The second view's WHERE clause must also be satisfied by any INSERT or UPDATE statements. To insert the row, it may be necessary to insert it directly into the underlying table, rather than through the view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no data found |
| Long Text: | In a host language program, all records have been fetched. The return code from the fetch was +4, indicating that all records have been returned from the SQL query. |
| Repair Text: | From Oracle doc: Terminate processing for the SELECT statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER COLUMN will make an index too large |
| Long Text: | Increasing the length of a column would cause the combined length of the columns specified in a previous CREATE INDEX statement to exceed the maximum index length (255). The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields are calculated as a length of 7, character fields are calculated at their defined width, and numeric fields are length 22. |
| Repair Text: | From Oracle doc: The only way to alter the column is to drop the affected index. The index cannot be re-created if to do so would exceed the maximum index width. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1405 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fetched column value is NULL |
| Long Text: | The INTO clause of a FETCH operation contained a NULL value, and no indicator was used. The column buffer in the program remained unchanged, and the cursor return code was +2. This is an error unless you are running Oracle with DBMS=6, emulating version 6, in which case it is only a warning. |
| Repair Text: | From Oracle doc: You may do any of the following: Use the NVL function to convert the retrieved NULL to another value, such as zero or blank. This is the simplest solution. Use an indicator to record the presence of the NULL. You probably should use this option when you want a specific action to be taken when a NULL arises. Revise the cursor definition so that no columns possibly containing NULL values are retrieved. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fetched column value was truncated |
| Long Text: | In a host language program, a FETCH operation was forced to truncate a character string. The program buffer area for this column was not large enough to contain the entire string. The cursor return code from the fetch was +3. |
| Repair Text: | From Oracle doc: Increase the column buffer area to hold the largest column value or perform other appropriate processing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot update mandatory NOT NULL column to NULL |
| Long Text: | An attempt was made to update data in a NOT NULL column to a NULL value. |
| Repair Text: | From Oracle doc: Specify a value for the column or modify the table definition to accept NULL values in that column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | such column list already indexed |
| Long Text: | A CREATE INDEX statement specified a column that is already indexed. A single column may be indexed only once. Additional indexes may be created on the column if it is used as a portion of a concatenated index, that is, if the index consists of multiple columns. |
| Repair Text: | From Oracle doc: Do not attempt to re-index the column, as it is unnecessary. To create a concatenated key, specify one or more additional columns in the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1409 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NOSORT option may not be used; rows are not in ascending order |
| Long Text: | Creation of index with NOSORT option when rows were not ascending. The NOSORT option may only be used for indexes on groups of rows that already are in ascending order. For non-unique indexes the ROWID is considered part of the index key. This means that two rows that appear to be stored in ascending order may not be. If you create an index NOSORT, and two of the rows in the table have the same index values, but get split across two extents, the data block address of the first block in the second extent can be less than the data block address of the last block in the first extent. If these addresses are not in ascending order, the ROWIDs are not either. Since these ROWIDs are considered part of the index key, the index key is not in ascending order, and the create index NOSORT fails. |
| Repair Text: | From Oracle doc: Create the index without the NOSORT option or ensure that the table is stored in one extent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1410 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ROWID |
| Long Text: | A ROWID was entered incorrectly. ROWIDs must be entered as formatted hexadecimal strings using only numbers and the characters A through F. A typical ROWID format is '000001F8.0001.0006'. |
| Repair Text: | From Oracle doc: Check the format, then enter the ROWID using the correct format. ROWID format: block ID, row in block, file ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1411 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot store the length of column in the indicator |
| Long Text: | An attempt was made to fetch a column of size more than 64K and could not store the length of the column in the given indicator of size 2 bytes. |
| Repair Text: | From Oracle doc: Use the new bind type with call backs to fetch the long column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1412 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | zero length not allowed for this datatype |
| Long Text: | The length for type 97 is 0. |
| Repair Text: | From Oracle doc: Specify the correct length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1413 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal value in packed decimal number buffer |
| Long Text: | The user buffer bound by the user as packed decimal number contained an illegal value. |
| Repair Text: | From Oracle doc: Use a legal value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1414 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid array length when trying to bind array |
| Long Text: | An attempt was made to bind an array without either a current array length pointer or a zero maximum array length. |
| Repair Text: | From Oracle doc: Specify a valid length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1415 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many distinct aggregate functions |
| Long Text: | The query contains more distinct aggregates than can be processed. The current limit is 255. |
| Repair Text: | From Oracle doc: Reduce the number of distinct aggregate functions in the query. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1416 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two tables cannot be outer-joined to each other |
| Long Text: | Two tables in a join operation specified an outer join with respect to each other. If an outer join is specified on one of the tables in a join condition, it may not be specified on the other table. |
| Repair Text: | From Oracle doc: Remove the outer join specification (+) from one of the tables, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1417 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a table may be outer joined to at most one other table |
| Long Text: | a.b (+) = b.b and a.c (+) = c.c is not allowed. |
| Repair Text: | From Oracle doc: Check that this is really what you want, then join b and c first in a view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1418 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified index does not exist |
| Long Text: | An ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement specified the name of an index that does not exist. Only existing indexes can be altered, dropped, or validated. Existing indexes may be listed by querying the data dictionary. |
| Repair Text: | From Oracle doc: Specify the name of an existing index in the ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1419 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datdts: illegal format code |
| Long Text: | An attempt was made to use an incorrect format. |
| Repair Text: | From Oracle doc: Inspect the format, correct it if necessary, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1420 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datstd: illegal format code |
| Long Text: | An attempt was made to use an invalid format. |
| Repair Text: | From Oracle doc: Inspect the format, correct it if necessary, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1421 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datrnd/dattrn: illegal precision specifier |
| Long Text: | An attempt was made to use an invalid precision specifier. |
| Repair Text: | From Oracle doc: Inspect the precision specifier, correct it if necessary, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1422 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exact fetch returns more than requested number of rows |
| Long Text: | The number specified in exact fetch is less than the rows returned. |
| Repair Text: | From Oracle doc: Rewrite the query or change number of rows requested. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1423 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error encountered while checking for extra rows in exact fetch |
| Long Text: | An error was encountered during the execution of an exact fetch. This message will be followed by more descriptive messages. |
| Repair Text: | From Oracle doc: See the accompanying messages and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1424 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or illegal character following the escape character |
| Long Text: | The character following the escape character in LIKE pattern is missing or not one of the escape character, '%', or '_'. |
| Repair Text: | From Oracle doc: Remove the escape character or specify the missing character. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1425 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | escape character must be character %s of length 1 |
| Long Text: | Given escape character for LIKE is not a character string of length 1. |
| Repair Text: | From Oracle doc: Change it to a character string of length 1. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1426 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | numeric overflow |
| Long Text: | Evaluation of an value expression causes an overflow/underflow. |
| Repair Text: | From Oracle doc: Reduce the operands. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1427 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | single-row subquery returns more than one row |
| Long Text: | The outer query must use one of the keywords ANY, ALL, IN, or NOT IN to specify values to compare because the subquery returned more than one row. |
| Repair Text: | From Oracle doc: Use ANY, ALL, IN, or NOT IN to specify which values to compare or reword the query so only one row is retrieved. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1428 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument '%s' is out of range |
| Long Text: | An illegal value for a mathematical function argument was specified. For example SELECT SQRT(-1) "Square Root" FROM DUAL; |
| Repair Text: | From Oracle doc: See the Oracle8i SQL Reference manual for valid input and ranges of the mathematical functions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1429 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Index-Organized Table: no data segment to store overflow row-pieces |
| Long Text: | No overflow segment defined. |
| Repair Text: | From Oracle doc: Add overflow segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column being added already exists in table |
| Long Text: | An ALTER TABLE ADD statement specified the name of a column that is already in the table. All column names must be unique within a table. |
| Repair Text: | From Oracle doc: Specify a unique name for the new column, then re-execute the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal inconsistency in GRANT command |
| Long Text: | An internal error occurred while attempting to execute a GRANT statement. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | public synonym to be dropped does not exist |
| Long Text: | The synonym specified in DROP PUBLIC SYNONYM is not a valid public synonym. It may be a private synonym. |
| Repair Text: | From Oracle doc: Correct the synonym name or use DROP SYNONYM if the synonym is not public. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | synonym to be created is already defined |
| Long Text: | A CREATE SYNONYM statement specified a synonym name that is the same as an existing synonym, table, view, or cluster. Synonyms may not have the same name as any other synonym, table, view, or cluster available to the user creating the synonym. |
| Repair Text: | From Oracle doc: Specify a unique name for the synonym, then re-execute the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1434 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | private synonym to be dropped does not exist |
| Long Text: | A DROP SYNONYM statement specified a synonym that does not exist. Existing synonym names may be listed by querying the data dictionary. |
| Repair Text: | From Oracle doc: Specify the name of an existing synonym in the DROP SYNONYM statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1435 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user does not exist |
| Long Text: | This message is caused by any reference to a non-existent user. For example, it occurs if a SELECT, GRANT, or REVOKE statement specifies a username that does not exist. Only a GRANT CONNECT statement may specify a new username. All other GRANT and REVOKE statements must specify existing usernames. If specified in a SELECT statement, usernames must already exist. |
| Repair Text: | From Oracle doc: Specify only existing usernames in the SELECT, GRANT, or REVOKE statement or ask the database administrator to define the new username. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CONNECT BY loop in user data |
| Long Text: | The condition specified in a CONNECT BY clause caused a loop in the query, where the next record to be selected is a descendent of itself. When this happens, there can be no end to the query. |
| Repair Text: | From Oracle doc: Check the CONNECT BY clause and remove the circular reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot have join with CONNECT BY |
| Long Text: | A join operation was specified with a CONNECT BY clause. If a CONNECT BY clause is used in a SELECT statement for a tree-structured query, only one table may be referenced in the query. |
| Repair Text: | From Oracle doc: Remove either the CONNECT BY clause or the join operation from the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value larger than specified precision allows for this column |
| Long Text: | When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column. |
| Repair Text: | From Oracle doc: Enter a value that complies with the numeric column's precision, or use the MODIFY option with the ALTER TABLE command to expand the precision. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1439 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column to be modified must be empty to change datatype |
| Long Text: | An ALTER TABLE MODIFY statement attempted to change the datatype of a column containing data. A column whose datatype is to be altered must contain only NULL values. |
| Repair Text: | From Oracle doc: To alter the datatype, first set all values in the column to NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column to be modified must be empty to decrease precision or scale |
| Long Text: | An ALTER TABLE MODIFY statement attempted to decrease the scale or precision of a numeric column containing data. In order to decrease either of these values, the column must contain only NULL values. An attempt to increase the scale without also increasing the precision will also cause this message. |
| Repair Text: | From Oracle doc: Set all values in the column to NULL before decreasing the numeric precision or scale. If attempting to increase the scale, increase the precision in accordance with the scale or set all values in the column to NULL first. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column to be modified must be empty to decrease column length |
| Long Text: | An ALTER TABLE MODIFY statement attempted to decrease the size of a character field containing data. A column whose maximum size is to be decreased must contain only NULL values. |
| Repair Text: | From Oracle doc: Set all values in column to NULL before decreasing the maximum size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1442 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | column to be modified to NOT NULL is already NOT NULL |
| Long Text: | An ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NOT NULL to NOT NULL. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal inconsistency; illegal datatype in resultant view column |
| Long Text: | An internal error occurred in referencing a view. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal inconsistency; internal datatype maps to invalid external type |
| Long Text: | This is an internal error message not normally issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1445 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot select ROWID from a join view without a key-preserved table |
| Long Text: | A SELECT statement attempted to select ROWIDs from a view derived from a join operation. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned. |
| Repair Text: | From Oracle doc: Remove ROWID from the view selection clause, then re-execute the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot select ROWID from view with DISTINCT, GROUP BY, etc. |
| Long Text: | A SELECT statement attempted to select ROWIDs from a view containing columns derived from functions or expressions. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned. |
| Repair Text: | From Oracle doc: Remove ROWID from the view selection clause, then re-execute the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1447 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER TABLE does not operate on clustered columns |
| Long Text: | An ALTER TABLE MODIFY statement specified a column used to cluster the table. Clustered columns may not be altered. |
| Repair Text: | From Oracle doc: To alter the column, first re-create the table in non-clustered form. The column's size can be increased at the same time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1448 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index must be dropped before changing to desired type |
| Long Text: | An ALTER TABLE MODIFY statement attempted to change an indexed character column to a LONG column. Columns with the datatype LONG may not be indexed, so the index must be dropped before the modification. |
| Repair Text: | From Oracle doc: Drop all indexes referencing the column before changing its datatype to LONG. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column contains NULL values; cannot alter to NOT NULL |
| Long Text: | An ALTER TABLE MODIFY statement attempted to change the definition of a column containing NULL values to NOT NULL. The column may not currently contain any NULL values if it is to be altered to NOT NULL. |
| Repair Text: | From Oracle doc: Set all NULL values in the column to values other than NULL before ALTERING the column to NOT NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1450 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum key length (%s) exceeded |
| Long Text: | The combined length of all the columns specified in a CREATE INDEX statement exceeded the maximum index length. The maximum index length varies by operating system. The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields have a length of 7, character fields have their defined length, and numeric fields have a length of 22. Numeric length = (precision/2) + 1. If negative, add +1. |
| Repair Text: | From Oracle doc: Select columns to be indexed so the total index length does not exceed the maximum index length for the operating system. See also your operating system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column to be modified to NULL cannot be modified to NULL |
| Long Text: | The column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint, or an ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NULL to NULL. |
| Repair Text: | From Oracle doc: If a primary key or check constraint is enforcing the NOT NULL constraint, then drop that constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot CREATE UNIQUE INDEX; duplicate keys found |
| Long Text: | A CREATE UNIQUE INDEX statement specified one or more columns that currently contain duplicate values. All values in the indexed columns must be unique by row to create a UNIQUE INDEX. |
| Repair Text: | From Oracle doc: If the entries need not be unique, remove the keyword UNIQUE from the CREATE INDEX statement, then re-execute the statement. If the entries must be unique, as in a primary key, then remove duplicate values before creating the UNIQUE index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SET TRANSACTION must be first statement of transaction |
| Long Text: | A transaction was not processed properly because the SET TRANSACTION statement was not the first statement. |
| Repair Text: | From Oracle doc: Commit or roll back the current transaction before using the statement SET TRANSACTION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1454 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot convert column into numeric datatype |
| Long Text: | A non-numeric value could not be converted into a number value. |
| Repair Text: | From Oracle doc: Check the value to make sure it contains only numbers, a sign, a decimal point, and the character "E" or "e", then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1455 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | converting column overflows integer datatype |
| Long Text: | The converted form of the specified expression was too large for the specified datatype. |
| Repair Text: | From Oracle doc: Define a larger datatype or correct the data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1456 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | may not perform insert/delete/update operation inside a READ ONLY transaction |
| Long Text: | A non-DDL insert/delete/update or select for update operation was attempted. |
| Repair Text: | From Oracle doc: Commit (or roll back) the transaction, and then re-execute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1457 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | converting column overflows decimal datatype |
| Long Text: | The converted form of the specified expression was too large for the specified type. The problem also occurs in COBOL programs when using COMP-3 in the picture clause, which is acceptable to the Pro*COBOL Precompiler and to COBOL but results in this error. |
| Repair Text: | From Oracle doc: Define a larger datatype or correct the data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1458 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid length inside variable character %s |
| Long Text: | An attempt was made to bind or define a variable character string with a buffer length less than the minimum requirement. |
| Repair Text: | From Oracle doc: Increase the buffer size or use a different type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1459 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid length for variable character %s |
| Long Text: | The buffer length was less than the minimum required or greater than its length at bind time minus two bytes. |
| Repair Text: | From Oracle doc: Make sure the string size is long enough to hold the buffer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1460 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unimplemented or unreasonable conversion requested |
| Long Text: | The requested format conversion is not supported. |
| Repair Text: | From Oracle doc: Remove the requested conversion from the SQL statement. Check the syntax for the TO_CHAR, TO_DATE, and TO_NUMBER functions to see which conversions are supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1461 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can bind a LONG value only for insert into a LONG column |
| Long Text: | An attempt was made to insert a value from a LONG datatype into another datatype. This is not allowed. |
| Repair Text: | From Oracle doc: Do not try to insert LONG datatypes into other types of columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1462 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot insert %s literals longer than 2000 characters |
| Long Text: | The longest literal supported by Oracle consists of 2000 characters. |
| Repair Text: | From Oracle doc: Reduce the number of characters in the literal to 2000 characters or fewer or use the VARCHAR2 or LONG datatype to insert strings exceeding 2000 characters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1463 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify column datatype with current constraint(s) |
| Long Text: | An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa. |
| Repair Text: | From Oracle doc: Remove the constraint(s) or do not perform the offending operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1464 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | circular grant (granting to grant ancestor) of table or view |
| Long Text: | The user in the TO clause of the GRANT statement has already been GRANTed privileges on this table. |
| Repair Text: | From Oracle doc: Do not GRANT privileges on a table to the user who originally GRANTed privileges on that table. The statement in error is probably unnecessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1465 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid hex number |
| Long Text: | In an UPDATE statement following a SELECT FOR UPDATE, part of the ROWID contains invalid characters. ROWID must be expressed in the proper and expected format for ROWID and within quotes. |
| Repair Text: | From Oracle doc: Enter the ROWID just as it was returned in the SELECT FOR UPDATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1466 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to read data - table definition has changed |
| Long Text: | This is a time-based read consistency error for a database object, such as a table or index. Either of the following may have happened: The query was parsed and executed with a snapshot older than the time the object was changed. The creation time-stamp of the object is greater than the current system time. This happens, for example, when the system time is set to a time earlier than the creation time of the object. |
| Repair Text: | From Oracle doc: If the cause is: an old snapshot, then commit or rollback the transaction and resume work. a creation time-stamp in the future, ensure the system time is set correctly. If the object creation time-stamp is still greater than the system time, then export the object's data, drop the object, re-create the object so it has a new creation time-stamp, import the object's data, and resume work. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1467 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sort key too long |
| Long Text: | A DISTINCT, GROUP BY, ORDER BY, or SET operation requires a sort key longer than that supported by Oracle. Either too many columns or too many group functions were specified in the SELECT statement. |
| Repair Text: | From Oracle doc: Reduce the number of columns or group functions involved in the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1468 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a predicate may reference only one outer-joined table |
| Long Text: | A predicate in the WHERE clause has two columns from different tables with "(+)". |
| Repair Text: | From Oracle doc: Change the WHERE clause so that each predicate has a maximum of one outer-join table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1469 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PRIOR can only be followed by a column name |
| Long Text: | An invalid column name was specified after the PRIOR keyword. |
| Repair Text: | From Oracle doc: Check syntax, spelling, use a valid column name, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1470 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | In-list iteration does not support mixed operators |
| Long Text: | Constants of different types are specified in an in-list. |
| Repair Text: | From Oracle doc: Use constants of same type for in-lists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1471 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a synonym with same name as object |
| Long Text: | An attempt was made to create a private synonym with the same name as the object to which it refers. This error typically occurs when a user attempts to create a private synonym with the same name as one of their objects. |
| Repair Text: | From Oracle doc: Choose a different synonym name or create the synonym under a different username. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1472 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc. |
| Long Text: | CONNECT BY cannot be used on a view where there is not a correspondence between output rows and rows of the underlying table. |
| Repair Text: | From Oracle doc: Remove the DISTINCT or GROUP BY from the view or move the CONNECT BY clause into the view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1473 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot have subqueries in CONNECT BY clause |
| Long Text: | Subqueries cannot be used in a CONNECT BY clause. |
| Repair Text: | From Oracle doc: Remove the subquery or move it to the WHERE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1474 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot have START WITH or PRIOR without CONNECT BY |
| Long Text: | START WITH and PRIOR are meaningful only in connection with CONNECT BY. |
| Repair Text: | From Oracle doc: Check the syntax for the SQL statement and add a CONNECT BY clause, if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1475 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must reparse cursor to change bind variable datatype |
| Long Text: | After executing a statement, an attempt was made to rebind a bind variable with a datatype different from that of the original bind. |
| Repair Text: | From Oracle doc: Re-parse the cursor before rebinding with a different datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1476 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | divisor is equal to zero |
| Long Text: | An expression attempted to divide by zero. |
| Repair Text: | From Oracle doc: Correct the expression, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1477 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user data area descriptor is too large |
| Long Text: | This is an internal error message not normally issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1478 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | array bind may not include any LONG columns |
| Long Text: | User is performing an array bind with a bind variable whose maximum size is greater than 2000 bytes. |
| Repair Text: | From Oracle doc: Such bind variables cannot participate in array binds. Use an ordinary bind operation instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1479 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | last character in the buffer is not Null |
| Long Text: | A bind variable of type 97 does not contain null at the last position. |
| Repair Text: | From Oracle doc: Make the last character null. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1480 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trailing null missing from STR bind value |
| Long Text: | A bind variable of type 5 (null-terminated string) does not contain the terminating null in its buffer. |
| Repair Text: | From Oracle doc: Terminate the string with a null character. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1481 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid number format model |
| Long Text: | An invalid format parameter was used with the TO_CHAR or TO_NUMBER function. |
| Repair Text: | From Oracle doc: Correct the syntax, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1482 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported character set |
| Long Text: | The second or third parameter to the CONVERT function is not a supported character set. |
| Repair Text: | From Oracle doc: Use one of the supported character sets. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1484 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | arrays can only be bound to PL/SQL statements |
| Long Text: | At attempt was made to bind an array to a non-PL/SQL statement. |
| Repair Text: | From Oracle doc: Rewrite the offending code being careful to bind arrays only to PL/SQL statements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1485 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | compile bind length different from execute bind length |
| Long Text: | You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length, given in the bind call. The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array. |
| Repair Text: | From Oracle doc: Ensure that the buffer size is sufficiently large to contain the array plus two bytes for the buffer length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1486 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | size of array element is too large |
| Long Text: | An attempt was made to bind a data value that was either too large for the datatype, for example, NUMBER, or was greater than 2000 bytes, for example, VARCHAR or LONG. |
| Repair Text: | From Oracle doc: Find a way to convert or truncate the data value so that its length is acceptable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1487 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | packed decimal number too large for supplied buffer |
| Long Text: | A conversion request cannot be performed because the buffer is too small to hold the result. |
| Repair Text: | From Oracle doc: Increase the size of the buffer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1488 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid nibble or byte in the input data |
| Long Text: | A conversion request cannot be performed because a digit was invalid. |
| Repair Text: | From Oracle doc: Fix the number and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1489 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | result of %s concatenation is too long |
| Long Text: | String concatenation result is more than the maximum size. |
| Repair Text: | From Oracle doc: Make sure that the result is less than the maximum size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1490 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid ANALYZE command |
| Long Text: | The syntax of the ANALYZE command was incorrect. |
| Repair Text: | From Oracle doc: Check the syntax and enter the command using the correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1491 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CASCADE option not valid |
| Long Text: | The CASCADE option should be used only for tables or clusters. |
| Repair Text: | From Oracle doc: Do not use the CASCADE option in this manner. Check the syntax of the statement and then retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1492 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LIST option not valid |
| Long Text: | The LIST option can be used only for tables or clusters. |
| Repair Text: | From Oracle doc: Do not use the LIST option in this manner. Check the syntax of the statement and then retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1493 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SAMPLE size specified |
| Long Text: | The specified SAMPLE size is out of range |
| Repair Text: | From Oracle doc: Specify a value within the proper range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1494 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SIZE specified |
| Long Text: | The specified histogram SIZE value was out of range. |
| Repair Text: | From Oracle doc: Specify a value within the proper range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1495 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified chain row table not found |
| Long Text: | The specified table either does not exist or user does not have the proper privileges. |
| Repair Text: | From Oracle doc: Specify the correct table to use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1496 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified chain row table form incorrect |
| Long Text: | The specified table does not have the proper field definitions. |
| Repair Text: | From Oracle doc: Specify the correct table to use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1497 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal option for ANALYZE CLUSTER |
| Long Text: | The FOR COLUMNS column_list clause cannot be used with ANALYZE CLUSTER. |
| Repair Text: | From Oracle doc: Retry with a legal syntax. For more information about ANALYZE CLUSTER, see Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1498 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | block check failure - see trace file |
| Long Text: | An error occurred while checking a block with the ANALYZE command. |
| Repair Text: | From Oracle doc: Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by the initialization parameter USER_DUMP_DEST. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to re-create the object. See also your operating system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1499 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table/index cross reference failure - see trace file |
| Long Text: | An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference. |
| Repair Text: | From Oracle doc: Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by the initialization parameter USER_DUMP_DEST. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to re-create the object. See also your operating system-specific Oracle documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure in getting date/time |
| Long Text: | During CREATE DATABASE or ALTER TABLESPACE, there was a failure in getting the date and time. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CREATE DATABASE failed |
| Long Text: | An error occurred during CREATE DATABASE. |
| Repair Text: | From Oracle doc: See accompanying errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index '%s.%s' or partition of such index is in unusable state |
| Long Text: | An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation. |
| Repair Text: | From Oracle doc: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CREATE CONTROLFILE failed |
| Long Text: | An error occurred during CREATE CONTROLFILE. |
| Repair Text: | From Oracle doc: See accompanying errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database name '%s' does not match parameter db_name '%s' |
| Long Text: | The name in a database create or mount does not match the name given in the initialization parameter DB_NAME. |
| Repair Text: | From Oracle doc: Correct or omit one of the two names. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in adding log files |
| Long Text: | During CREATE or ALTER DATABASE, error(s) occurred when adding new log files. |
| Repair Text: | From Oracle doc: Check error stack for detailed error information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or illegal database name |
| Long Text: | No database name was specified in the CREATE/ALTER DATABASE statement, and no DB_NAME initialization parameter was specified. |
| Repair Text: | From Oracle doc: Either the database name must be given in the statement or in the DB_NAME initialization parameter. Note that the SVRMGR or SQL*PLUS STARTUP command issues an ALTER DATABASE statement using the database name specified as part of STARTUP (if any). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database not mounted |
| Long Text: | A command was attempted that requires the database to be mounted. |
| Repair Text: | From Oracle doc: If you are using the ALTER DATABASE statement via the SVRMGR or SQL*PLUS STARTUP command, specify the MOUNT option to restart; else if you are directly doing an ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to ALTER DATABASE. If you are doing a backup or copy, you must first mount the desired database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create database; error in file '%s' at line %s |
| Long Text: | CREATE DATABASE was unable to process the specified file. |
| Repair Text: | From Oracle doc: Check the offending line in the specified file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified name '%s' does not match actual '%s' |
| Long Text: | The database name specified in ALTER DATABASE does not match the name of the currently mounted database. |
| Repair Text: | From Oracle doc: Correct the database name spelling or DISMOUNT the mounted database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in deleting log files |
| Long Text: | During ALTER DATABASE, an error occurred while dropping log files. |
| Repair Text: | From Oracle doc: Check the error stack for detailed error information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in renaming log/data files |
| Long Text: | During ALTER DATABASE, an error occurred while renaming log or datafiles. |
| Repair Text: | From Oracle doc: Check the error stack for detailed error information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error renaming log file %s - new file %s not found |
| Long Text: | An attempt to change a log file's name in the control file failed because no file was found with the new name. |
| Repair Text: | From Oracle doc: Make sure that the log file has been properly renamed by the operating system and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid current time returned by operating system |
| Long Text: | The operating system returned a time that was not between 1988 and 2121. |
| Repair Text: | From Oracle doc: Correct the time kept by the operating system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in log specification: no such log |
| Long Text: | A log file name, or list of member names, did not correspond to an existing log. |
| Repair Text: | From Oracle doc: Specify an existing log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1515 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error dropping log group %s: no such log |
| Long Text: | ALTER DATABASE is attempting to drop a log file which is not known to the database control file. |
| Repair Text: | From Oracle doc: Specify the name of an existing log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1516 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | nonexistent log file, datafile or tempfile '%s' |
| Long Text: | An attempt was made to use ALTER DATABASE to either rename a log file or datafile, or change attributes of a datafile or temporary file. The attempt failed because the specified file is not known to the database's control file or is not a type supported for the request. |
| Repair Text: | From Oracle doc: Specify the name of an existing file of the correct type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1517 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log member: '%s' |
| Long Text: | This message indicates the filename involved with other messages. |
| Repair Text: | From Oracle doc: See the accompanying messages and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1518 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CREATE DATABASE must specify more than one log file |
| Long Text: | Only one log file was specified in the CREATE DATABASE statement. |
| Repair Text: | From Oracle doc: Specify at least two log files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1519 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while processing file '%s' near line %s |
| Long Text: | CREATE DATABASE encountered a problem while processing specified file. The specified file is bad. |
| Repair Text: | From Oracle doc: Retry your system installation procedure or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1520 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of data files to add (%s) exceeds limit of %s |
| Long Text: | CREATE TABLESPACE statement specifies more files than is permitted for this database. |
| Repair Text: | From Oracle doc: Use fewer files or re-create the database with a larger value of MAXDATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1521 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in adding data files |
| Long Text: | During CREATE or ALTER TABLESPACE, an error was detected while adding datafiles. |
| Repair Text: | From Oracle doc: Check the error stack for detailed error information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1522 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file '%s' to be renamed does not exist |
| Long Text: | During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file. |
| Repair Text: | From Oracle doc: Specify the correct file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1523 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot rename data file to '%s' - file already part of database |
| Long Text: | During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file. |
| Repair Text: | From Oracle doc: Rename the file to a name not already being used as part of the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1524 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create data file as '%s' - file already part of database |
| Long Text: | During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file. |
| Repair Text: | From Oracle doc: Create the file as a name not already being used as part of the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1525 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in renaming data files |
| Long Text: | An error occurred when renaming files as part of ALTER TABLESPACE. |
| Repair Text: | From Oracle doc: Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1526 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in opening file '%s' |
| Long Text: | CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error. |
| Repair Text: | From Oracle doc: Retry your system installation procedure or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1527 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while reading file |
| Long Text: | CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error. |
| Repair Text: | From Oracle doc: Retry your system installation procedure or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1528 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EOF while processing SQL statement |
| Long Text: | CREATE DATABASE unexpectedly hit EOF while reading the specified file. The SQL.BSQ file is bad. |
| Repair Text: | From Oracle doc: Retry your system installation procedure or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1529 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error closing file '%s' |
| Long Text: | CREATE DATABASE was not able to close the specified file. |
| Repair Text: | From Oracle doc: Retry your system installation procedure or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1530 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a database already mounted by the instance |
| Long Text: | During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance in which a database is or has previously been mounted. |
| Repair Text: | From Oracle doc: If you wish to mount the database, shut down and then restart the instance and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1531 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a database already open by the instance |
| Long Text: | During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database. |
| Repair Text: | From Oracle doc: If you wish to open a new database on the instance, first shut down and then restart the instance and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1532 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create database; instance being started elsewhere |
| Long Text: | During CREATE DATABASE, another user appears to be simultaneously altering the instance. |
| Repair Text: | From Oracle doc: Make sure no one else is simultaneously altering the instance. If no one is, contact Oracle Customer Support; otherwise, retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1533 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot rename file '%s'; file does not belong to tablespace |
| Long Text: | During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace. |
| Repair Text: | From Oracle doc: Specify the correct file name or the correct tablespace name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment '%s' doesn't exist |
| Long Text: | During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown. |
| Repair Text: | From Oracle doc: Use the correct rollback segment name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1535 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment '%s' already exists |
| Long Text: | Specified rollback segment already exists. |
| Repair Text: | From Oracle doc: Use a different name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1536 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | space quota exceeded for tablespace '%s' |
| Long Text: | The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace. |
| Repair Text: | From Oracle doc: Either drop unnecessary objects in the tablespace to reclaim space or have a privileged user increase the quota on this tablespace for the segment owner. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1537 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add data file '%s' - file already part of database |
| Long Text: | During CREATE or ALTER TABLESPACE, a file being added is already part of the database. |
| Repair Text: | From Oracle doc: Use a different file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1538 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to acquire any rollback segment |
| Long Text: | Failed to acquire any rollback segment during startup in shared mode. |
| Repair Text: | From Oracle doc: Restart in exclusive mode to create one more public segment or specify available private segments in the initialization parameter. ROLLBACK_SEGMENTS_REQUIRED, then start in shared mode |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1539 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is not online |
| Long Text: | Failed to either make a tablespace read only or offline because it is not online. A tablespace must be online before it can become read only or offline normal. |
| Repair Text: | From Oracle doc: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1540 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is not offline |
| Long Text: | Failed to bring a tablespace online because it is not offline. |
| Repair Text: | From Oracle doc: Check the status of the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1541 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system tablespace cannot be brought offline; shut down if necessary |
| Long Text: | An attempt was made to bring system tablespace offline. |
| Repair Text: | From Oracle doc: Shut down if necessary to do recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1542 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is offline, cannot allocate space in it |
| Long Text: | An attempt was made to allocate space in an offline tablespace. |
| Repair Text: | From Oracle doc: Bring the tablespace online or create the object in other tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1543 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' already exists |
| Long Text: | An attempt was made to create a tablespace which already exists. |
| Repair Text: | From Oracle doc: Use a different name for the new tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1544 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot drop system rollback segment |
| Long Text: | An attempt was made to drop system rollback segment. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1545 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment '%s' specified not available |
| Long Text: | One of the following: An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. An attempt was made to drop a rollback segment that is currently online. An attempt was made to alter a rollback segment that is currently online to use unlimited extents. |
| Repair Text: | From Oracle doc: One of the following: Make the rollback segment available; for example, bring an offline tablespace online. Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment. Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions. Same as 3). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1546 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace contains active rollback segment '%s' |
| Long Text: | An attempt was made to make a tablespace that contains active rollback segment(s) offline or read only. |
| Repair Text: | From Oracle doc: Shut down instances that use the active rollback segments in the tablespace and then make the tablespace offline or read only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1547 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | warning: RECOVER succeeded but OPEN RESETLOGS would get error below |
| Long Text: | Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery. |
| Repair Text: | From Oracle doc: Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1548 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | active rollback segment '%s' found, terminate dropping tablespace |
| Long Text: | An attempt was made to drop a tablespace that contains active rollback segment(s). |
| Repair Text: | From Oracle doc: Shut down instances that use the active rollback segments in the tablespace and then drop the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1549 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace not empty, use INCLUDING CONTENTS option |
| Long Text: | An attempt was made to drop a non-empty tablespace. |
| Repair Text: | From Oracle doc: To drop all the objects in the tablespace, use the INCLUDING CONTENTS option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1550 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot drop system tablespace |
| Long Text: | An attempt was made to drop system tablespace. This is not allowed. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1551 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | extended rollback segment, pinned blocks released |
| Long Text: | Doing recursive extent of rollback segment, trapped internally by the system. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use system rollback segment for non-system tablespace '%s' |
| Long Text: | An attempt was made to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database. |
| Repair Text: | From Oracle doc: Create one or more private/public segment(s), shut down and restart. May need to modify the initialization parameter ROLLBACK_SEGMENTS to acquire private rollback segment. If this is a clone database being used for tablespace point in time recovery then this operation is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1553 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXEXTENTS must be no smaller than the %s extents currently allocated |
| Long Text: | The number of extents allocated is greater than the MAXEXTENTS specified. |
| Repair Text: | From Oracle doc: Specify a larger MAXEXTENTS value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1554 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | out of transaction slots in transaction tables |
| Long Text: | Too many concurrent transactions. |
| Repair Text: | From Oracle doc: Shut down the system, modify the initialization parameters TRANSACTIONS, ROLLBACK_SEGMENTS or ROLLBACK_SEGMENTS_REQUIRED, and then restart. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1555 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot too old: rollback segment number %s with name "%s" too small |
| Long Text: | Rollback records needed by a reader for consistent read are overwritten by other writers. |
| Repair Text: | From Oracle doc: Use larger rollback segments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1556 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MINEXTENTS for rollback segment must be greater than 1 |
| Long Text: | Specified MINEXTENTS of less than 2 for rollback segment. |
| Repair Text: | From Oracle doc: Specify larger MINEXTENTS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1557 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment extents must be at least %s blocks |
| Long Text: | Specified extent of less than minimum size for rollback segment. |
| Repair Text: | From Oracle doc: Specify larger extents. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1558 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | out of transaction ID's in rollback segment %s |
| Long Text: | All the available transaction IDs have been used. |
| Repair Text: | From Oracle doc: Shut down the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction IDs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1559 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXEXTENTS for rollback segment must be greater than 1 |
| Long Text: | Specified MAXEXTENTS of less than 2 for rollback segment. |
| Repair Text: | From Oracle doc: Specify larger MAXEXTENTS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1560 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | global hash table size mismatch for %s (%s != %s) |
| Long Text: | The specified "GC_" initialization parameter was incompatible with that of another instance which already has the database mounted. |
| Repair Text: | From Oracle doc: Fix the "GC_" parameter and restart. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1561 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to remove all objects in the tablespace specified |
| Long Text: | Failed to remove all objects when dropping a tablespace. |
| Repair Text: | From Oracle doc: Retry the drop tablespace until all objects are dropped. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1562 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to extend rollback segment number %s |
| Long Text: | Failure occurred when trying to extend rollback segment. |
| Repair Text: | From Oracle doc: This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintenance. Use SELECT SEGMENT_NAME FROM DBA_ROLLBACK_SEGS WHERE SEGMENT_ID=string (where string is the segment number from the message) to determine the rollback segment name. Then use the ALTER ROLLBACK SEGMENT OFFLINE command to take the rollback segment offline. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1563 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment is PUBLIC, need to use the keyword PUBLIC |
| Long Text: | Did not use the keyword PUBLIC to identified public rollback segment. |
| Repair Text: | From Oracle doc: Use the keyword PUBLIC when identifying public rollback segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1564 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment is not PUBLIC |
| Long Text: | The rollback segment identified is not public. |
| Repair Text: | From Oracle doc: Do not use the keyword PUBLIC when identifying private rollback segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1565 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in identifying file '%s' |
| Long Text: | An error occurred while trying to identify a file. |
| Repair Text: | From Oracle doc: Check the error stack for detailed information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1566 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file specified more than once in DROP LOGFILE |
| Long Text: | The list of files supplied to DROP LOGFILE contains at least one duplicate. |
| Repair Text: | From Oracle doc: Remove the duplicate file specification and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1567 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dropping log %s would leave less than 2 log files in thread %s |
| Long Text: | Dropping all the logs specified would leave fewer than the required two log files per enabled thread. |
| Repair Text: | From Oracle doc: Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1568 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot set space quota on PUBLIC |
| Long Text: | An attempt was made to set space quota on a tablespace for PUBLIC. |
| Repair Text: | From Oracle doc: If trying to grant system-wide or tablespace-wide space privileges to all users, use GRANT RESOURCE [ON tablespace] TO PUBLIC. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1569 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file too small for system dictionary tables |
| Long Text: | The datafile specified during creation of the database is too small to hold the system dictionary tables. |
| Repair Text: | From Oracle doc: Re-create the database by specifying a larger file or more files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1570 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MINEXTENTS must be no larger than the %s extents currently allocated |
| Long Text: | The number of extents allocated is smaller than the MINEXTENTS specified. |
| Repair Text: | From Oracle doc: Specify a smaller MINEXTENTS value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1571 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | redo version %s incompatible with ORACLE version %s |
| Long Text: | This software version cannot read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery. |
| Repair Text: | From Oracle doc: Shut down and restart using the compatible software. Do any required media recovery, and open the database. Shut down and restart using the current software. If the file is going to be dropped then take it offline with the DROP option to skip this check. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1572 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment %s cannot be brought online, %s extents exceeded |
| Long Text: | The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing. |
| Repair Text: | From Oracle doc: Drop and re-create the rollback segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1573 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | shutting down instance, no further change allowed |
| Long Text: | Some process tried to make changes while the database was being shut down. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1574 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of concurrent transactions exceeded |
| Long Text: | The limit on the number of concurrent transactions has been hit. |
| Repair Text: | From Oracle doc: Shut down the system, increase the value of the initialization parameter TRANSACTIONS, and then restart the system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1575 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | timeout waiting for space management resource |
| Long Text: | Failed to acquire necessary resource to do space management. |
| Repair Text: | From Oracle doc: Retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1576 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | instance locking protocol version %s incompatible with ORACLE version %s |
| Long Text: | Current software uses incompatible locking protocol. |
| Repair Text: | From Oracle doc: Upgrade software used to start instances so that they use compatible locking protocol. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1577 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add log file '%s' - file already part of database |
| Long Text: | During CREATE or ALTER DATABASE, a file being added is already part of the database. |
| Repair Text: | From Oracle doc: Use a different file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1578 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE data block corrupted (file # %s, block # %s) |
| Long Text: | The data block indicated was corrupted, probably due to program errors. |
| Repair Text: | From Oracle doc: Determine which object was corrupted using a command like the following: SELECT SEGMENT_TYPE,OWNER||'.'||SEGMENT_NAME FROM DBA_EXTENTS
Try to restore the segment containing the block indicated. This may involve dropping the segment and re-creating it. If there is a trace file, report the errors in it to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1579 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | write error occurred during recovery |
| Long Text: | A write error occurred during recovery. |
| Repair Text: | From Oracle doc: Consult trace files for the nature of the write error, and correct error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1580 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error creating control backup file %s |
| Long Text: | An operating system error occurred while attempting to create a control file backup. |
| Repair Text: | From Oracle doc: Check the error stack for more detailed information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1581 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to use rollback segment (%s) new extent (%s) which is being allocated |
| Long Text: | Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent which has not been completely allocated. |
| Repair Text: | From Oracle doc: The rollback segment extending will be rolled back by the system, no more extension will be possible until the next extent is freed up by rolling back or committing other transactions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1582 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to open controlfile for backup |
| Long Text: | An operating system error occurred while attempting to open a control file for backup. |
| Repair Text: | From Oracle doc: Check the error stack for more detailed information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1583 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to get block size of controlfile to be backed up |
| Long Text: | An operating system error occurred while attempting to get the block size of a control file for backup. |
| Repair Text: | From Oracle doc: Check the error stack for more detailed information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1584 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to get file size of controlfile to be backed up |
| Long Text: | An operating system error occurred while attempting to get the file size of a control file for backup. |
| Repair Text: | From Oracle doc: Check the error stack for more detailed information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1585 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error identifying backup file %s |
| Long Text: | An operating system error occurred when attempting to identify the file to be used for control file backup. |
| Repair Text: | From Oracle doc: Check the error stack for more detailed information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1586 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to open destination file %s for backup |
| Long Text: | An operating system error occurred while attempting to open a control file for backup. |
| Repair Text: | From Oracle doc: Check the error stack for more detailed information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1587 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error during controlfile backup file copy |
| Long Text: | An operating system error occurred while attempting to copy a control file for backup. |
| Repair Text: | From Oracle doc: Check the accompanying message stack for detailed information and then take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1588 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must use RESETLOGS option for database open |
| Long Text: | An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup. |
| Repair Text: | From Oracle doc: Use the RESETLOGS option when opening the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1589 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must use RESETLOGS or NORESETLOGS option for database open |
| Long Text: | Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database. |
| Repair Text: | From Oracle doc: Specify the appropriate option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1590 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of segment free list (%s) exceeds maximum of %s |
| Long Text: | The value of the storage parameter FREELIST GROUPS is too large. |
| Repair Text: | From Oracle doc: Reduce the value of the storage parameter FREELIST GROUPS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1591 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | lock held by in-doubt distributed transaction %s |
| Long Text: | An attempt was made to access resource that is locked by a dead two-phase commit transaction that is in prepared state. |
| Repair Text: | From Oracle doc: The database administrator should query the PENDING_TRANS$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, the database administrator should contact the database administrator at the commit point if known or the end user for correct outcome, or use heuristic default if given to issue a heuristic COMMIT or ABORT command to finalize the local portion of the distributed transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1592 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error converting Version 7 rollback segment (%s) to Oracle 8 format |
| Long Text: | Look at the accompanying internal error; Version 7 database may not have shut down cleanly. |
| Repair Text: | From Oracle doc: Investigate the internal error; may have to reload the Version 7 database (from backup) and shut down the database cleanly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1593 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment optimal size (%s blks) is smaller than the computed initial size (%s blks) |
| Long Text: | Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment. |
| Repair Text: | From Oracle doc: Specify a larger OPTIMAL size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1594 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to wrap into rollback segment (%s) extent (%s) which is being freed |
| Long Text: | Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and/or there are too many extents to free. |
| Repair Text: | From Oracle doc: The rollback segment shrinking will be rolled back by the system; increase the optimal size of the rollback segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1595 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error freeing extent (%s) of rollback segment (%s)) |
| Long Text: | Some error occurred while freeing inactive rollback segment extents. |
| Repair Text: | From Oracle doc: Investigate the accompanying error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1596 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify system in %s parameter |
| Long Text: | The system rollback segment is specified in the initialization parameter referred to in the error message. |
| Repair Text: | From Oracle doc: Change the value of the initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1597 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot alter system rollback segment online or offline |
| Long Text: | An attempt was made to online or offline the system rollback segment. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1598 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment '%s' is not online |
| Long Text: | Could have been taken offline before by the database administrator or cleaned up by SMON. |
| Repair Text: | From Oracle doc: Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS to make sure the rollback segment is actually online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1599 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to acquire rollback segment (%s), cache space is full (currently has (%s) entries) |
| Long Text: | The amount statically allocated is not enough based on the value of the MAX_ROLLBACK_SEGMENTS parameter. |
| Repair Text: | From Oracle doc: For now, take another rollback segment offline or increase the value of the parameter MAX_ROLLBACK_SEGMENTS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | at most one "%s" in clause "%s" of %s |
| Long Text: | The initialization parameter was incorrectly specified. |
| Repair Text: | From Oracle doc: Correct the initialization parameter and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal bucket size in clause "%s" of %s |
| Long Text: | The bucket size was invalid for this parameter. |
| Repair Text: | From Oracle doc: Correct the initialization parameter and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1603 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal grouping size in clause "%s" of %s |
| Long Text: | The grouping size was invalid for this parameter. |
| Repair Text: | From Oracle doc: Correct the initialization parameter and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1604 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal number range in clause "%s" of %s |
| Long Text: | The number range was invalid for this parameter. |
| Repair Text: | From Oracle doc: Correct the initialization parameter and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1605 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing numbers in clause "%s" of %s |
| Long Text: | The numbers were missing for this parameter. |
| Repair Text: | From Oracle doc: Correct the initialization parameter and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | gc_files_to_locks not identical to that of another mounted instance |
| Long Text: | The GC_FILES_TO_LOCKS parameters were different on two instances. |
| Repair Text: | From Oracle doc: Modify the initialization parameter GC_FILES_TO_LOCKS and restart. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1607 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | gc_lck_procs (%s) is not the same as other instances (%s) |
| Long Text: | The GC_LCK_PROCS initialization parameter is not the same as in other instances that already have the database open. |
| Repair Text: | From Oracle doc: Modify the GC_LCK_PROCS parameter and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1608 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot bring rollback segment '%s' online, its status is (%s) |
| Long Text: | Could have been brought online before by the database administrator or left as a result of process crash. |
| Repair Text: | From Oracle doc: Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1609 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s is the current log for thread %s - cannot drop members |
| Long Text: | A member of the current log for a thread cannot be dropped. |
| Repair Text: | From Oracle doc: If the thread is opened, request a log switch by the instance that is using it. If it is not open, disable the thread, manually archive the log, or clear it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1610 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recovery using the BACKUP CONTROLFILE option must be done |
| Long Text: | Either an earlier database recovery session specified BACKUP CONTROLFILE, or the control file was re-created with the RESETLOGS option, or the control file being used is a backup control file. After that only BACKUP CONTROLFILE recovery is allowed and it must be followed by a log reset at the next database open. |
| Repair Text: | From Oracle doc: Perform recovery using the BACKUP CONTROFILE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1611 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread number %s is invalid - must be between 1 and %s |
| Long Text: | A thread number in a command is greater than the number of threads supported by the control file. |
| Repair Text: | From Oracle doc: Use a thread number that is valid, or resize the thread record and/or checkpoint progress record sections of the control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1612 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s is already enabled |
| Long Text: | An attempt was made to enable a thread that is already enabled. |
| Repair Text: | From Oracle doc: Either use this thread or enable another thread. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1613 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s only has %s logs - at least 2 logs required to enable |
| Long Text: | The thread cannot be enabled because it only has two online log files associated with it. |
| Repair Text: | From Oracle doc: Add logs to the thread or pick another thread to enable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1614 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | thread %s is busy - cannot enable |
| Long Text: | The mount enqueue for the thread could not be acquired when attempting to enable the thread. This probably means that another process has already started enabling this thread. |
| Repair Text: | From Oracle doc: Wait and try again, or find another thread to enable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1615 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s is mounted - cannot disable |
| Long Text: | Some instance, possibly this one, has allocated the thread for its use. The thread may not be disabled while in use. |
| Repair Text: | From Oracle doc: Shut down cleanly the instance using the thread. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1616 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s is open - cannot disable |
| Long Text: | The thread is not closed. The last instance to use the thread died leaving the thread open. A thread cannot be disabled until it is closed. It is still required for crash or instance recovery. |
| Repair Text: | From Oracle doc: If the database is open, instance recovery should close the thread soon; wait a few minutes. Otherwise open the database; crash recovery will close the thread. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1617 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot mount: %s is not a valid thread number |
| Long Text: | The value of the initialization parameter THREAD is not between 1 and the number of threads allowed by the control file. |
| Repair Text: | From Oracle doc: Shut down the instance, change the value of the initialization parameter and restart, or resize the thread record and/or checkpoint progress record sections of the control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1618 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s is not enabled - cannot mount |
| Long Text: | The value of the initialization parameter THREAD requests a thread that is not enabled. A thread must be enabled before it can be mounted. |
| Repair Text: | From Oracle doc: Shut down the instance, change the value of the initialization parameter and restart, mounting a different thread. If the database is open in another instance, then the thread may be enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1619 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread %s is mounted by another instance |
| Long Text: | The value of the initialization parameter THREAD requests a thread that has been mounted by another instance. Only one instance may use a thread. |
| Repair Text: | From Oracle doc: Shut down the instance, change the value of the initialization parameter and restart, mounting a different thread. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1620 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no public threads are available for mounting |
| Long Text: | The value of the initialization parameter THREAD is zero, its default value. There are no threads which have been publicly enabled, and not mounted. |
| Repair Text: | From Oracle doc: Shut down the instance, change the value of the initialization parameter to a thread which is privately enabled and not mounted. If the database is open in another instance, then a thread may be publicly enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1621 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot rename member of current log if database is open |
| Long Text: | This is a rename command for a member of the current log for an open thread. If the database is open anywhere, the log may be in use, so the rename cannot be done. |
| Repair Text: | From Oracle doc: Wait until the log is not current, or mount the database exclusively. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1622 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | thread number must be specified - default not specific |
| Long Text: | The thread was not specified when adding a log, and the currently mounted thread was chosen by default at mount time. Since the current thread was not specified explicitly the user cannot know which thread the log will be added to. |
| Repair Text: | From Oracle doc: Explicitly specify the thread number either in the initialization parameter THREAD, or in the ADD command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1623 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s is current log for thread %s - cannot drop |
| Long Text: | A thread's current log cannot be dropped even if the thread is closed. A disabled thread usually does not have a current log, but a half completed disable may need to be disabled again. |
| Repair Text: | From Oracle doc: If the database is not open then disable the thread. If the database is open and an instance has the thread open, then the instance can be requested to switch logs. If the database is closed the log can be archived or cleared to force a switch. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1624 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s needed for crash recovery of thread %s |
| Long Text: | A log cannot be dropped or cleared until the thread's checkpoint has advanced out of the log. |
| Repair Text: | From Oracle doc: If the database is not open then open it. Crash recovery will advance the checkpoint. If the database is open force a global checkpoint. If the log is corrupted so that the database cannot be opened, it may be necessary to do incomplete recovery until cancel at this log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1625 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment '%s' does not belong to this instance |
| Long Text: | An attempt was made to shrink or take a rollback segment offline that does not belong to this instance. |
| Repair Text: | From Oracle doc: Take only those rollback segments offline that belong to the current instance. To take the rollback segment offline, connect to the instance containing it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1626 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment number '%s' cannot handle more transactions |
| Long Text: | Too many transactions in this segment. |
| Repair Text: | From Oracle doc: Choose a different rollback segment, or reduce the number of concurrent transactions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1627 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment number '%s' is not online |
| Long Text: | Could have been taken offline before by the database administrator or cleaned up by SMON. |
| Repair Text: | From Oracle doc: Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS to make sure the rollback segment is actually online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1628 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached for rollback segment %s |
| Long Text: | An attempt was made to extend a rollback segment that was already at the MAXEXENTS value. |
| Repair Text: | From Oracle doc: If the value of the MAXEXTENTS storage parameter is less than the maximum allowed by the system, raise this value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1629 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached saving undo for tablespace %s |
| Long Text: | Save undo for the offline tablespace at MAXEXTENTS. |
| Repair Text: | From Oracle doc: Check the storage parameters for the system tablespace. The tablespace needs to be brought back online so the undo can be applied. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1630 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in temp segment in tablespace %s |
| Long Text: | A temporary segment tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS for the tablespace is less than the system maximum, you can raise that. Otherwise, raise PCTINCREASE for the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1631 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in table %s.%s |
| Long Text: | A table tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1632 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in index %s.%s |
| Long Text: | An index tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If the value of MAXEXTENTS in the index storage clause is less than the maximum (based on your block size), raise it. Otherwise, re-create the index with larger extent sizes so that the total number of extents falls below the maximum. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1633 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel Server Option needed for this operation |
| Long Text: | System does not have parallel server configured. |
| Repair Text: | From Oracle doc: Obtain parallel server option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1634 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment number '%s' is about to go offline |
| Long Text: | The rollback segment specified was marked to go offline by the database administrator. |
| Repair Text: | From Oracle doc: Bring the rollback segment online first. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1635 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment #%s specified not available |
| Long Text: | One of the following: You tried to acquire an offline rollback segment during startup. You tried to drop a rollback segment that contains active transactions. |
| Repair Text: | From Oracle doc: For the above, one of the following: Bring the tablespace containing the rollback segment online or do not specify the rollback segment in the initialization parameter file. If the rollback segment is in use, shut down the instance using the rollback segment. Otherwise, if the rollback segment needs recovery, determine which errors are holding back the rolling back of the transactions and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1636 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment '%s' is already online |
| Long Text: | A rollback segment can only be used by one instance and an instance is trying to bring a rollback segment online that is already in use. |
| Repair Text: | From Oracle doc: Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See the Oracle8i Administrator's Guide for more information about using rollback segments in parallel mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1637 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment '%s' is being used by another instance (#%s) |
| Long Text: | A rollback segment can only be used by one instance, and an instance is trying to access a rollback segment online that is already in use. |
| Repair Text: | From Oracle doc: Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See Oracle8i Administrator's Guide for more information about using rollback segments in parallel mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1638 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s does not allow ORACLE version %s to mount parallel |
| Long Text: | The value of the RECOVERY_COMPATIBLE parameter is set too low to allow this software version to do a parallel mount. |
| Repair Text: | From Oracle doc: Either use an earlier software release or advance the RECOVERY_COMPATIBLE parameter. If this happens when no RECOVERY_COMPATIBLE parameter has been specified then set it to the current software release. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1639 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database cannot be mounted parallel with no lock processes |
| Long Text: | The value of GC_LCK_PROCS is 0, and the database is being mounted in parallel mode. |
| Repair Text: | From Oracle doc: Change GC_LCK_PROCS to a value between 1 and 10, or leave it undefined to use the built-in default. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1640 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot make tablespace read only with active transactions |
| Long Text: | An attempt was made to make a tablespace read only while there are active transactions in the database. All transactions must commit or rollback to insure that there is no undo for a tablespace before it can be made read only. This includes in doubt distributed transactions. |
| Repair Text: | From Oracle doc: Prevent any more transactions from being started. Putting the database in restricted mode usually helps. If there are any in doubt transactions they must also be resolved. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1641 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is not online - cannot add data file |
| Long Text: | An attempt was made to add a datafile to a tablespace that has been set to read only or offline. |
| Repair Text: | From Oracle doc: Make the tablespace online and read write then add the datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1642 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | begin backup not needed for read only tablespace '%s' |
| Long Text: | An attempt was made to begin or end a backup for a tablespace that has been set to read only. |
| Repair Text: | From Oracle doc: Take the backup without any BEGIN or END commands. The files are not being modified so the backup will be consistent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1643 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system tablespace can not be made read only |
| Long Text: | An attempt was made to set the system tablespace to read only. The system tablespace must remain read write for database operation. |
| Repair Text: | From Oracle doc: Leave system tablespace read write. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1644 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is already read only |
| Long Text: | An attempt was made to make tablespace read only that is already read only. |
| Repair Text: | From Oracle doc: Leave tablespace read only, or make read write then make read only again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1645 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | previous attempt to make read write is half complete |
| Long Text: | A failure while making the tablespace read write left it read only, but the checkpoint was advanced. The tablespace will not be usable after a resetlogs if its files are offline. |
| Repair Text: | From Oracle doc: Repeat the command to make the tablespace read write. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1646 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is not read only - cannot make read write |
| Long Text: | An attempt was made to make a tablespace read write that is not read only. It may be either online or offline. |
| Repair Text: | From Oracle doc: Leave tablespace read write. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1647 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is read only, cannot allocate space in it |
| Long Text: | An attempt was made to allocate space in a read-only tablespace. |
| Repair Text: | From Oracle doc: Create the object in another tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1648 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s is the current log of disabled thread %s |
| Long Text: | An attempt to enable the thread failed after it was half completed. This log was left as the current log even though the thread is still disabled. Since a log switch cannot be done until the thread is enabled, the log cannot be cleared or archived. |
| Repair Text: | From Oracle doc: Complete the thread enable by issuing the ENABLE command again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1649 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | operation not allowed with a backup controlfile |
| Long Text: | An attempt is being made to perform a command that does not make sense when the control file is a restored backup. |
| Repair Text: | From Oracle doc: Wait until after the database has been opened and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1650 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend rollback segment %s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for rollback segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1651 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend save undo segment by %s for tablespace %s |
| Long Text: | Failed to allocate an extent for saving undo entries for the indicated offline tablespace. |
| Repair Text: | From Oracle doc: Check the storage parameters for the SYSTEM tablespace. The tablespace needs to be brought back online so the undo can be applied. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1652 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend temp segment by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for temporary segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1653 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend table %s.%s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for table segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1654 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend index %s.%s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for index segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1655 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend cluster %s.%s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for cluster segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1656 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in cluster %s.%s |
| Long Text: | A cluster tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1657 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SHRINK option value |
| Long Text: | The specified value must be an integer. |
| Repair Text: | From Oracle doc: Choose an appropriate integer value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1658 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to create INITIAL extent for segment in tablespace %s |
| Long Text: | Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1659 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to allocate MINEXTENTS beyond %s in tablespace %s |
| Long Text: | Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1660 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is already permanent |
| Long Text: | An attempt was made to make tablespace permanent that is already permanent. |
| Repair Text: | From Oracle doc: Leave tablespace permanent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1661 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is already temporary |
| Long Text: | An attempt was made to make tablespace temporary that is already temporary. |
| Repair Text: | From Oracle doc: Leave tablespace permanent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1662 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is non-empty and cannot be made temporary |
| Long Text: | An attempt was made to convert a non-empty tablespace to a temporary tablespace |
| Repair Text: | From Oracle doc: Drop all the objects in the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1663 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the contents of tablespace '%s' is constantly changing |
| Long Text: | The contents of the tablespace is always changing between PERMANENT and TEMPORARY. |
| Repair Text: | From Oracle doc: Decide what the tablespace contents should be and stay with it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1664 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Transaction which has expanded the Sort Segment has aborted |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1665 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile is not a standby controlfile |
| Long Text: | An attempt was made to mount, recover or activate a standby database without a standby control file. |
| Repair Text: | From Oracle doc: Create a standby control file before attempting to use the database as a standby database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1666 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile is for a standby database |
| Long Text: | An attempt was made to mount, recover, or open a standby database without the appropriate command option to designate a standby database. |
| Repair Text: | From Oracle doc: Use the standby option or appropriate commands, or mount with the primary control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1667 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add any more tablespaces: limit of %s exceeded |
| Long Text: | There is no more room in the control file for adding tablespaces. |
| Repair Text: | From Oracle doc: Resize the control file or drop other tablespaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1668 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby database requires DROP option for offline of data file |
| Long Text: | An attempt was made to take a datafile offline in a standby database without specifying the DROP option. Files that are offline in a standby database are not recovered, and are likely to be unusable if the standby is activated. Note that specifying DROP does not prevent bringing the file online later. |
| Repair Text: | From Oracle doc: Specify the DROP option or leave the file online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1669 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby database controlfile not consistent |
| Long Text: | An attempt was made to activate a standby database with a control file that has not been recovered to the same point as the datafiles. Most likely the control file was just copied from the primary database and has not been used for recovery. |
| Repair Text: | From Oracle doc: Recover the standby database until all the files are consistent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1670 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new datafile %s needed for standby database recovery |
| Long Text: | Standby database recovery noticed that a file was added to the primary database, but is not available on the standby. |
| Repair Text: | From Oracle doc: Either copy the file from the primary database or do an ALTER DATABASE CREATE DATAFILE command on the standby to create a file to recover. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1671 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile is a backup, cannot make a standby controlfile |
| Long Text: | The currently mounted control file is a backup control file, and attempting to create a control file for a standby database. |
| Repair Text: | From Oracle doc: Complete any needed recovery and open the database with the resetlogs option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1672 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile may be missing files or have extra ones |
| Long Text: | An attempt was made to create a standby control file, but the control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus the datafiles in the control file and the ones in the data dictionary may not match. |
| Repair Text: | From Oracle doc: Open the database, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1673 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file %s has not been identified |
| Long Text: | This datafile was not in the control file after an incomplete recovery or CREATE CONTROLFILE. Since information from its header is needed for standby database recovery, we cannot create a standby control file. |
| Repair Text: | From Oracle doc: Find the file and bring it online. If desired it may be taken offline again. If you intend to drop this file, then taking it offline with the DROP option will avoid this error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1674 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data file %s is an old incarnation rather than current file |
| Long Text: | Recovery encountered redo that indicates this file was dropped from the database and another file was added using the same file number. This implies that a CREATE CONTROLFILE command was given the old file which was dropped rather than the latest file. |
| Repair Text: | From Oracle doc: Rebuild the control file using CREATE CONTROLFILE, and give the correct file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1675 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max_commit_propagation_delay inconsistent with other instances |
| Long Text: | The MAX_COMMIT_PROPAGATION_DELAY initialization parameter is inconsistent with those in other instances. |
| Repair Text: | From Oracle doc: Make sure all instances have the same MAX_COMMIT_PROPAGATION_DELAY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1676 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby file name convert of '%s' exceeds maximum length of %s |
| Long Text: | When the given file name is converted to the name used for the standby database, the converted name is bigger than the maximum allowed file name. |
| Repair Text: | From Oracle doc: Change the value of the initialization parameter DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1677 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby file name convert parameters differ from other instance |
| Long Text: | The DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT initialization parameters are not the same as in other instances that already have the database mounted. |
| Repair Text: | From Oracle doc: Change the value of the initialization parameters DB_FILE_STANDBY_NAME_CONVERT and LOG_FILE_STANDBY_NAME_CONVERT to match other instances. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1678 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s must be two strings, a pattern and a replacement |
| Long Text: | The initialization parameter does not have two strings for its value. The first string it a pattern to be found in file names. The second string is used to replace the pattern when found in file names. |
| Repair Text: | From Oracle doc: Specify two strings for the parameter, or omit the parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1679 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database must be mounted EXCLUSIVE and not open to activate |
| Long Text: | An attempt to activate a standby database was made when the database was not mounted EXCLUSIVE or was already open. |
| Repair Text: | From Oracle doc: Mount the database EXCLUSIVE and retry the ACTIVATE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1680 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend LOB segment by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for a LOB segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1681 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in LOB segment in tablespace %s |
| Long Text: | A LOB segment tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS for the tablespace is less than the system maximum, you can raise that. Otherwise, raise PCTINCREASE for the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1682 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | read-only DB cannot allocate temporary space in tablespace %s |
| Long Text: | Temporary space (usually for sorting) could not be allocated in either main storage or a temporary file. An attempt was made to allocate the space from the tablespace named, but the database is opened read only. The database open requires a sort work space. |
| Repair Text: | From Oracle doc: Either allow sufficient workspace in main storage (SORT_AREA_SIZE initialization parameter), or create a temporary tablespace before making the database read only. Use ALTER TABLESPACE ADD TEMPFILE statement to add temporary files to the temporary tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1683 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend index %s.%s partition %s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for index segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1684 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in table %s.%s partition %s |
| Long Text: | A table tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1685 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in index %s.%s partition %s |
| Long Text: | An index tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1686 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # files (%s) reached for the tablespace %s |
| Long Text: | The number of files for a given tablespace has reached its maximum value. |
| Repair Text: | From Oracle doc: Resize existing files in the tablespace, or partition the objects among multiple tablespaces, or move some objects to a different tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1687 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified logging attribute for tablespace '%s' is same as the existing |
| Long Text: | An attempt was made to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute. |
| Repair Text: | From Oracle doc: Change the specified logging attribute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1688 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend table %s.%s partition %s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for table segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1689 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in clause "%s" of %s |
| Long Text: | There was a syntax in the initialization parameter. |
| Repair Text: | From Oracle doc: Fix the syntax error and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1690 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | gc_rollback_locks not identical to that of another mounted instance |
| Long Text: | The parameter GC_ROLLBACK_LOCKS was different on different instances. |
| Repair Text: | From Oracle doc: Modify the initialization parameter GC_ROLLBACK_LOCKS and restart. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1691 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend lob segment %s.%s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for LOB segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1692 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend lob segment %s.%s partition %s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for LOB segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1693 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in lob segment %s.%s |
| Long Text: | A LOB segment tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1694 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in lob segment %s.%s partition %s |
| Long Text: | A LOB segment tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1695 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error converting rollback segment %s to version 8.0.2 |
| Long Text: | Version 8.0.1 database may not have shut down cleanly. |
| Repair Text: | From Oracle doc: May have to reload the 8.0.1 database and shut down cleanly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1696 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile is not a clone controlfile |
| Long Text: | An attempt was made to mount, a database as a clone when it is already mounted by another instance not as a clone or attempting to use a current control file for a clone. |
| Repair Text: | From Oracle doc: Mount without the clone option or use a backup control file and shut down the other instances before mounting as a clone. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1697 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile is for a clone database |
| Long Text: | An attempt was made to mount a clone database without the appropriate command option to designate a clone database. |
| Repair Text: | From Oracle doc: Use the clone option or appropriate commands, or mount with the primary control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1698 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a clone database may only have SYSTEM rollback segment online |
| Long Text: | An attempt was made to online a rollback segment in a clone database. |
| Repair Text: | From Oracle doc: Do not use this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1699 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | tablespace '%s' is being imported for point in time recovery |
| Long Text: | An attempt was made to online a tablespace or begin another point in time import while a point in time import is already in progress. |
| Repair Text: | From Oracle doc: Wait until the import completes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1700 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate username in list |
| Long Text: | A username was listed twice in a GRANT or REVOKE statement. Usernames must be unique and may only be specified once in a GRANT or REVOKE statement. |
| Repair Text: | From Oracle doc: Remove the duplicate username and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a cluster is not appropriate here |
| Long Text: | The name of a cluster was specified in a statement in which clusters are not permitted. |
| Repair Text: | From Oracle doc: Enter a valid CLUSTER statement or change the cluster name to the name of a valid object for the statement, such as table, view, index, or synonym. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a view is not appropriate here |
| Long Text: | The name of a view was specified in a statement in which views are not permitted. |
| Repair Text: | From Oracle doc: Enter the name of a valid object for the statement, such as table, cluster, synonym, or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing SYNONYM keyword |
| Long Text: | The keyword SYNONYM is required in this context. |
| Repair Text: | From Oracle doc: Check the statement syntax and insert the keyword SYNONYM. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s literal too long |
| Long Text: | The string literal is longer than 4000 characters. |
| Repair Text: | From Oracle doc: Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an outer join cannot be specified on a correlation column |
| Long Text: | A correlation column, that is, a column in a subquery from a table referenced in the outer query's FROM clause, was followed by an outer-join indicator (+). This is not allowed. |
| Repair Text: | From Oracle doc: Revise the query. Refer to the syntax for subqueries. The outer-join indicator may follow only columns in the same query block in which their table is included in the FROM clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user function result value was too large |
| Long Text: | The user-written SQL function has generated a result that is larger than the maximum defined in the function table. |
| Repair Text: | From Oracle doc: Change the maximum in the function table or correct the user-written function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1707 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing LIST keyword |
| Long Text: | The keyword LIST is required in this context, for example, when using the ARCHIVE LOG statement to display the set of redo log files. |
| Repair Text: | From Oracle doc: Check the statement syntax, insert the keyword LIST where required, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ACCESS or SESSION expected |
| Long Text: | An AUDIT or NOAUDIT statement contained the keyword BY followed by something other than ACCESS or SESSION. |
| Repair Text: | From Oracle doc: Check the statement syntax and make sure to follow the keyword BY with ACCESS or SESSION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | program does not exist |
| Long Text: | This feature is not currently implemented. |
| Repair Text: | From Oracle doc: No user action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1710 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing OF keyword |
| Long Text: | The keyword OF was not specified in a SELECT FOR UPDATE statement. |
| Repair Text: | From Oracle doc: Check and correct the statement syntax. To specify SELECT FOR UPDATE, add the following clause to the end of the SELECT statement: |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1711 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate privilege listed |
| Long Text: | A privilege was listed twice in a GRANT or REVOKE statement. A privilege may be specified only once in these statements. |
| Repair Text: | From Oracle doc: Remove the duplicate privilege from the list and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1712 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot grant a privilege grantor does not have |
| Long Text: | The grantor could not grant a privilege to another user because the grantor does not have the privilege. A grantor can grant only privileges that the grantor has or is authorized to grant. |
| Repair Text: | From Oracle doc: Either Specify only authorized privileges in the GRANT statement. Ask the database administrator to grant the user the required privileges. Ask the database administrator for the required privileges and then grant the other user the privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1713 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GRANT OPTION does not exist for that privilege |
| Long Text: | A GRANT statement specified a privilege that the granting user has but is not authorized to grant to other users. When the user was granted the privilege, the user was not given the GRANT OPTION needed to grant those privileges to others. |
| Repair Text: | From Oracle doc: Change the GRANT statement to specify only authorized privileges or ask the user who granted the privileges to grant the GRANT OPTION also. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1714 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in execution of user function |
| Long Text: | The user-written SQL function indicated that an error occurred during its execution. The meaning of the message is function-dependent. |
| Repair Text: | From Oracle doc: Ensure proper usage of the function or correct the function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1715 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNIQUE may not be used with a cluster index |
| Long Text: | An attempt was made to create a cluster index with the UNIQUE attribute. |
| Repair Text: | From Oracle doc: Remove UNIQUE from the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1716 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NOSORT may not be used with a cluster index |
| Long Text: | An attempt was made to create a cluster index using the NOSORT option. |
| Repair Text: | From Oracle doc: Remove NOSORT from the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1717 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | seccta invalid access mode token passed |
| Long Text: | This is an internal error message not normally issued. |
| Repair Text: | From Oracle doc: Contact customer support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1718 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | BY ACCESS | SESSION clause not allowed for NOAUDIT |
| Long Text: | Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement. |
| Repair Text: | From Oracle doc: Remove BY ACCESS | SESSION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1719 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | outer join operator (+) not allowed in operand of OR or IN |
| Long Text: | An outer join appears in an or clause. |
| Repair Text: | From Oracle doc: If A and B are predicates, to get the effect of (A(+) or B), try (select where (A(+) and not B)) union all (select where (B)). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1720 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | grant option does not exist for '%s.%s' |
| Long Text: | A grant was being performed on a view and the grant option was not present for an underlying object. |
| Repair Text: | From Oracle doc: Obtain the grant option on all underlying objects of the view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1721 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | USERENV(COMMITSCN) invoked more than once in a transaction |
| Long Text: | The USERENV('COMMITSCN') function can only be used once in a transaction. |
| Repair Text: | From Oracle doc: Re-write the transaction to use USERENV('COMMITSCN') only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1722 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number |
| Long Text: | The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates. |
| Repair Text: | From Oracle doc: Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1723 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | zero-length columns are not allowed |
| Long Text: | During CREATE TABLE, a zero-length column was specified, for example, CHAR(0). |
| Repair Text: | From Oracle doc: Correct the column declaration so that the length is at least 1 and try the operation again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1724 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | floating point precision is out of range (1 to 126) |
| Long Text: | Floating point precision is too small or large. |
| Repair Text: | From Oracle doc: Correct and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1725 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | USERENV('COMMITSCN') not allowed here |
| Long Text: | The function USERNEV('COMMMITSCN') is only allowed as a top-level expression in the VALUES clause of an INSERT statements, and on the right hand side of an assignment in an UPDATE statement. |
| Repair Text: | From Oracle doc: Correct the use of the function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1726 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a table is not appropriate here |
| Long Text: | A table name was used in a statement in which tables are not permitted. |
| Repair Text: | From Oracle doc: Enter a valid table statement or use the current statement on the appropriate object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1727 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | numeric precision specifier is out of range (1 to 38) |
| Long Text: | The precision specified for a number column in a CREATE/ALTER TABLE or CREATE CLUSTER statement must be a digit between 1 and 38. If no precision is specified, a default precision of 22 digits is used. |
| Repair Text: | From Oracle doc: Specify numeric precision between 1 and 38 and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1728 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | numeric scale specifier is out of range (-84 to 127) |
| Long Text: | The scale specified for a numeric field in a CREATE/ALTER TABLE or CREATE CLUSTER statement is not in the valid range. It should be between -84 and 127. |
| Repair Text: | From Oracle doc: Specify a numeric scale between -84 and 127. If a number is not specified, the default scale of the column is 0 decimal places. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1729 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | database link name expected |
| Long Text: | A database link name does not follow the at-sign (@) in a reference to a table in a remote database. |
| Repair Text: | From Oracle doc: Correct the reference and retry the operation. The correct syntax for denoting a table in a remote database follows: username.table_name@ database_name
|
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1730 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number of column names specified |
| Long Text: | The number of column names specified in a CREATE VIEW statement did not correspond to the number of columns listed in the SELECT clause. If column names are specified in a CREATE VIEW statement, exactly one name must be specified for each column or expression in the SELECT clause. |
| Repair Text: | From Oracle doc: Specify one view column name for each column in the SELECT clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1731 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | circular view definition encountered |
| Long Text: | Through a series of CREATE and DROP VIEW statements, a view was defined that refers to itself. For example, VIEW1 might include a column from VIEW2 that is defined as a column in VIEW1. View definitions may be seen by querying the data dictionary. |
| Repair Text: | From Oracle doc: Check the view definitions, remove any circular references, and retry the statements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1732 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data manipulation operation not legal on this view |
| Long Text: | An attempt was made to use an UPDATE, INSERT, or DELETE statement on a view that contains expressions or functions or was derived from more than one table. If a join operation was used to create the view or the view contains virtual columns derived from functions or expressions, then the view may only be queried. |
| Repair Text: | From Oracle doc: UPDATE, INSERT, or DELETE rows in the base tables instead and restrict the operations on the view to queries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1733 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | virtual column not allowed here |
| Long Text: | An attempt was made to use an INSERT, UPDATE, or DELETE statement on an expression in a view. |
| Repair Text: | From Oracle doc: INSERT, UPDATE, or DELETE data in the base tables, instead of the view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1734 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | illegal parameters - EXTENT MIN higher than EXTENT MAX |
| Long Text: | An incorrect value is specified for the parameter. |
| Repair Text: | From Oracle doc: Correct the parameter and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1735 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid ALTER TABLE option |
| Long Text: | An invalid option was specified in an ALTER TABLE statement. |
| Repair Text: | From Oracle doc: Check the statement syntax, specify a valid option, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1736 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | [NOT] SUCCESSFUL expected |
| Long Text: | An AUDIT or NOAUDIT statement contained WHENEVER followed by something other than SUCCESSFUL or NOT SUCCESSFUL. |
| Repair Text: | From Oracle doc: Correct the WHENEVER clause and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1737 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE |
| Long Text: | The lock mode entered was not recognized. |
| Repair Text: | From Oracle doc: Enter one of the following: SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, SHARE ROW EXCLUSIVE, or SHARE UPDATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1738 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing IN keyword |
| Long Text: | In a LOCK TABLE statement, the keyword IN was missing. |
| Repair Text: | From Oracle doc: Place the keyword IN and lock mode directly after the table name in the LOCK TABLE statement and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1739 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing MODE keyword |
| Long Text: | In a LOCK TABLE statement, the keyword MODE was missing. The keyword MODE must directly follow the specified lock mode. |
| Repair Text: | From Oracle doc: Check the statement syntax, insert the keyword MODE where required, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1740 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing double quote in identifier |
| Long Text: | An initial double quote (") was found without a closing quote. If an identifier contains a blank or special characters other than $, #, or _, it must be enclosed in double quotes. |
| Repair Text: | From Oracle doc: Add a closing double quote (") to the end of the identifier. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1741 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal zero-length identifier |
| Long Text: | An attempt was made to use two double quotes ("") as an identifier. An identifier must be at least one character long. |
| Repair Text: | From Oracle doc: Insert at least one character between the double quotes in the identifier. If a blank identifier is required, specify a blank space between the double quotes (" "). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1742 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | comment not terminated properly |
| Long Text: | The indicated comment or hint begun with the /* token did not have the terminating */. |
| Repair Text: | From Oracle doc: Properly terminate the comment or hint with a */. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1743 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only pure functions can be indexed |
| Long Text: | The indexed function uses SYSDATE or the user environment. |
| Repair Text: | From Oracle doc: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL expressions must not use SYSDATE, USER, USERENV(), or anything else dependent on the session state. NLS-dependent functions are OK. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1744 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | inappropriate INTO |
| Long Text: | The INTO clause may not be used in a subquery. |
| Repair Text: | From Oracle doc: Check the syntax, place the INTO clause in the top-level query, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1745 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid host/bind variable name |
| Long Text: | A colon in a bind variable or INTO specification was followed by an inappropriate name, perhaps a reserved word. |
| Repair Text: | From Oracle doc: Change the variable name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1746 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | indicator variable not permitted here |
| Long Text: | An indicator variable is not permitted in this context. |
| Repair Text: | From Oracle doc: Remove the indicator variable and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1747 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid user.table.column, table.column, or column specification |
| Long Text: | A column name was specified improperly in the current SQL statement. |
| Repair Text: | From Oracle doc: Check the statement's syntax, especially references to column names, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1748 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only simple column names allowed here |
| Long Text: | This SQL statement does not allow a qualified column name, such as username.table.column or table.column. |
| Repair Text: | From Oracle doc: Remove the qualifications from the column and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1749 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | you may not GRANT/REVOKE privileges to/from yourself |
| Long Text: | Grantor is not allowed to grant or revoke object or system privileges to self. |
| Repair Text: | From Oracle doc: Issue the GRANT or REVOKE of system privileges from another database administrator account. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1750 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column |
| Long Text: | Although it is possible to GRANT update privileges on a column-by-column basis, it is only possible to REVOKE them for an entire table. |
| Repair Text: | From Oracle doc: Do not identify specific columns. To revoke update privileges for certain columns, use REVOKE for the entire table and GRANT the user privileges for specific columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1751 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Invalid dump undo option |
| Long Text: | An invalid option is specified in the ALTER DUMP UNDO command. |
| Repair Text: | From Oracle doc: Correct and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1752 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot delete from view without exactly one key-preserved table |
| Long Text: | The deleted table either had no key preserved tables, had more than one key-preserved table, or the key-preserved table was an unmerged view or a table from a read-only view. |
| Repair Text: | From Oracle doc: Redefine the view or delete it from the underlying base tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1753 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column definition incompatible with clustered column definition |
| Long Text: | When adding a table to a cluster, the definition of the column in the table was inconsistent with the definition of the column in the cluster. |
| Repair Text: | From Oracle doc: The table cannot be added to the cluster until all cluster column definitions are consistent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1754 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a table may contain only one column of type LONG |
| Long Text: | An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped. |
| Repair Text: | From Oracle doc: Remove the LONG column currently in the table by using the ALTER TABLE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1755 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Must specify an extent number or block number |
| Long Text: | Expecting an extent or block number but something else was specified. |
| Repair Text: | From Oracle doc: Correct the error and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1756 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | quoted %s not properly terminated |
| Long Text: | A quoted string must be terminated with a single quote mark ('). |
| Repair Text: | From Oracle doc: Insert the closing quote and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1757 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Must specify an object number |
| Long Text: | Expecting an object number but something else was specified. |
| Repair Text: | From Oracle doc: Correct the error and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1758 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table must be empty to add mandatory (NOT NULL) column |
| Long Text: | It is not possible to define a new column as NOT NULL if rows already exist in the table being modified. |
| Repair Text: | From Oracle doc: Retry the statement without the NOT NULL specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1759 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user function is incorrectly defined |
| Long Text: | A user function has been improperly defined. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1760 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal argument for function |
| Long Text: | The argument or arguments specified for the function are not valid in this context. |
| Repair Text: | From Oracle doc: Check the definition of the function and correct the arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1761 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DML operation does not map to a unique table in the join |
| Long Text: | The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table. |
| Repair Text: | From Oracle doc: Change the join specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1762 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | vopdrv: view query block not in FROM |
| Long Text: | This is an internal error message not normally issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1763 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | update or delete involves outer joined table |
| Long Text: | For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer- joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table. |
| Repair Text: | From Oracle doc: Change the join specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1764 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new update value of join is not guaranteed to be unique |
| Long Text: | A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated. |
| Repair Text: | From Oracle doc: Change the join specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1765 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specifying table's owner name is not allowed |
| Long Text: | A table or view name was specified with a period (.) or identified with an invalid prefix. |
| Repair Text: | From Oracle doc: Check that the object is identified correctly and if necessary remove the period from the name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1766 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dictionary table not allowed in this context |
| Long Text: | The name of a data dictionary object was used outside the FROM clause of a SELECT statement. The only operation allowed on a data dictionary object is to SELECT from it. |
| Repair Text: | From Oracle doc: Restrict operations on data dictionary objects to queries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1767 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | UPDATE ... SET expression must be a subquery |
| Long Text: | An attempt was made to use a single expression without a subquery to update a list of columns. |
| Repair Text: | From Oracle doc: Check the syntax for using subqueries to update data and add the necessary subquery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1768 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number %s too long |
| Long Text: | A number entered exceeds the limit of 255 characters, including digits, sign, decimal point, and exponent. |
| Repair Text: | From Oracle doc: Shorten the number string, perhaps by expressing it in scientific notation, for example, 1.85E9 instead of 1,850,000,000. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1769 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate CLUSTER option specifications |
| Long Text: | During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option. |
| Repair Text: | From Oracle doc: Remove the extra CLUSTER option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1770 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CLUSTER option not allowed in CREATE CLUSTER command |
| Long Text: | An attempt was made to use the CLUSTER option within a CREATE CLUSTER statement. |
| Repair Text: | From Oracle doc: Remove the CLUSTER clause and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1771 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal option for a clustered table |
| Long Text: | During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE, CACHE, NOCACHE. These options may only be specified for the cluster itself. |
| Repair Text: | From Oracle doc: Remove the illegal option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1772 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Must specify a value for LEVEL |
| Long Text: | Expecting the value of LEVEL but something else was specified. |
| Repair Text: | From Oracle doc: Correct the error and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1773 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | may not specify column datatypes in this CREATE TABLE |
| Long Text: | Column datatypes were specified in a SELECT statement used to create and load a table directly. |
| Repair Text: | From Oracle doc: Remove column datatypes. The datatypes of the SELECT list expressions are automatically used as the column datatypes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1774 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Dump undo option specified more than once |
| Long Text: | The same option for ALTER DUMP UNDO was specified twice. |
| Repair Text: | From Oracle doc: Remove the redundant options and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1775 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | looping chain of synonyms |
| Long Text: | Through a series of CREATE synonym statements, a synonym was defined that referred to itself. For example, the following definitions are circular: CREATE SYNONYM s1 for s2 |
| Repair Text: | From Oracle doc: Change one synonym definition so that it applies to a base table or view and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1776 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify more than one base table through a join view |
| Long Text: | Columns belonging to more than one underlying table were either inserted into or updated. |
| Repair Text: | From Oracle doc: Phrase the statement as two or more separate statements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1777 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | WITH GRANT OPTION not allowed in this system |
| Long Text: | This version of Oracle does not support the WITH GRANT OPTION. |
| Repair Text: | From Oracle doc: Remove the WITH GRANT option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1778 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum subquery nesting level exceeded |
| Long Text: | An attempt was made to use more than 255 levels of nested subqueries. |
| Repair Text: | From Oracle doc: Merge some of the subqueries into their containing queries, until there are less than 255 levels of nesting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1779 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify a column which maps to a non key-preserved table |
| Long Text: | An attempt was made to insert or update columns of a join view which map to a non-key-preserved table. |
| Repair Text: | From Oracle doc: Modify the underlying base tables directly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1780 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s literal required |
| Long Text: | In a COMMENT statement, the Comment following the keyword IS must be a quoted string literal. |
| Repair Text: | From Oracle doc: Check that the Comment is a string literal. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1781 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNRECOVERABLE cannot be specified without AS SELECT |
| Long Text: | UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause. |
| Repair Text: | From Oracle doc: Do not specify UNRECOVERABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1782 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNRECOVERABLE cannot be specified for a cluster or clustered table |
| Long Text: | A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE. |
| Repair Text: | From Oracle doc: Do not specify UNRECOVERABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1783 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one RECOVERABLE or UNRECOVERABLE clause may be specified |
| Long Text: | RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement. |
| Repair Text: | From Oracle doc: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1784 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RECOVERABLE cannot be specified with database media recovery disabled |
| Long Text: | A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created. |
| Repair Text: | From Oracle doc: Do not specify RECOVERABLE, or restart the database with media recovery enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1785 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORDER BY item must be the number of a SELECT-list expression |
| Long Text: | Either an ORDER BY item for a set expression is not a column number, or the ORDER BY item is not the number of a SELECT list column. |
| Repair Text: | From Oracle doc: The ORDER BY item must be a number between 1 and the number of columns in the SELECT list. Check the column number and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1786 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | FOR UPDATE of this query expression is not allowed |
| Long Text: | An attempt was made to use a FOR UPDATE clause on the result of a set expression involving GROUP BY, DISTINCT, UNION, INTERSECT, or MINUS. |
| Repair Text: | From Oracle doc: Check the syntax, remove the FOR UPDATE clause, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1787 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one clause allowed per query block |
| Long Text: | An attempt was made to use more than one WHERE, GROUP BY, CONNECT BY, or HAVING clause in the query. |
| Repair Text: | From Oracle doc: Combine the duplicate clauses into a single clause and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1788 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | CONNECT BY clause required in this query block |
| Long Text: | A START WITH clause was specified without a CONNECT BY clause. |
| Repair Text: | From Oracle doc: Check the syntax, specify a CONNECT BY clause, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1789 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | query block has incorrect number of result columns |
| Long Text: | All of the queries participating in a set expression do not contain the same number of SELECT list columns. |
| Repair Text: | From Oracle doc: Check that all the queries in the set expression have the same number of SELECT list columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1790 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | expression must have same datatype as corresponding expression |
| Long Text: | A SELECT list item corresponds to a SELECT list item with a different datatype in another query of the same set expression. |
| Repair Text: | From Oracle doc: Check that all corresponding SELECT list items have the same datatypes. Use the TO_NUMBER, TO_CHAR, and TO_DATE functions to do explicit data conversions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1791 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a SELECTed expression |
| Long Text: | There is an incorrect ORDER BY item. The query is a SELECT DISTINCT query with an ORDER BY clause. In this context, all ORDER BY items must be constants, SELECT list expressions, or expressions whose operands are constants or SELECT list expressions. |
| Repair Text: | From Oracle doc: Remove the inappropriate ORDER BY item from the SELECT list and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1792 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of columns in a table or view is 1000 |
| Long Text: | While creating a table or view, more than 1000 columns were specified. |
| Repair Text: | From Oracle doc: Remove some columns from the table or view definition. If all the information is required, split the columns into two tables or views and join the columns when querying. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1793 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of index columns is 32 |
| Long Text: | While creating an index, more than 32 columns were specified. |
| Repair Text: | From Oracle doc: Remove some columns from the index definition. If all the columns indexed are required, split them into two indexes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1794 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of cluster columns is 32 |
| Long Text: | More than 32 columns were specified in the cluster key. |
| Repair Text: | From Oracle doc: Remove some of the columns from the cluster key definition. Consider concatenating multiple character strings into a single column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1795 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of expressions in a list is 1000 |
| Long Text: | More than 254 columns or expressions were specified in a list. |
| Repair Text: | From Oracle doc: Remove some of the expressions from the list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1796 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this operator cannot be used with lists |
| Long Text: | A relational operator is not allowed in this context. When comparing lists, use only an operator that tests for equivalence, such as =, !=, or IN. |
| Repair Text: | From Oracle doc: Rephrase the query so that it only compares lists for equivalence. For example, the following clause is invalid: WHERE (A,B) > ((C,D), (E,F))
|
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1797 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | this operator must be followed by ANY or ALL |
| Long Text: | The keyword ANY or ALL was missing. |
| Repair Text: | From Oracle doc: Check the statement syntax and add ANY or ALL where appropriate. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1798 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing EXCEPTION keyword |
| Long Text: | The EXCEPTION keyword is missing from the ENABLE clause. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1799 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a column may not be outer-joined to a subquery |
| Long Text: | expression(+) relop (subquery) is not allowed. |
| Repair Text: | From Oracle doc: Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a literal in the date format was too large to process |
| Long Text: | A literal specified in a date format was too large. If a literal is entered as a date, it must be less than 220 characters long. |
| Repair Text: | From Oracle doc: Use only literals less than 220 characters long in the date format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | date format is too long for internal buffer |
| Long Text: | The date format string was too long to process. This should occur only if several long literals are specified as part of a date. |
| Repair Text: | From Oracle doc: Remove long literals from the date format string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Julian date is out of range |
| Long Text: | An invalid Julian date was entered. Valid Julian dates run from 1 to 3,442,447. |
| Repair Text: | From Oracle doc: Enter a valid Julian date between 1 and 3,442,447. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure in getting date/time |
| Long Text: | This is an internal error message that is not likely to occur. It is usually caused by a failure in the system clock. |
| Repair Text: | From Oracle doc: Investigate the system clock and the process that requested the date or time. If necessary, contact customer support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | format code appears twice |
| Long Text: | A format code was listed twice in a date specification. Each format code may be specified only once in the function TO_DATE. |
| Repair Text: | From Oracle doc: Remove the duplicate format code from the date specification, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Julian date precludes use of day of year |
| Long Text: | Both a Julian date and a day of the year were specified in the TO_DATE function. If a Julian date is specified, the day of the year (DDD) may not be specified, as it is contained in the Julian date. |
| Repair Text: | From Oracle doc: Remove the day of the year or the Julian date from the specification, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | year may only be specified once |
| Long Text: | More than one year format code was listed in a date specification. Only one of the following year format codes may be specified in a date: YYYY, YYY, YY, Y. |
| Repair Text: | From Oracle doc: Remove all but one year format from the date specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hour may only be specified once |
| Long Text: | More than one hour format code was listed in a date specification. Only one of the following hour format codes may be specified in a date: HH, HH12, HH24. |
| Repair Text: | From Oracle doc: Remove all but one hour format from the date specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1814 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | AM/PM conflicts with use of A.M./P.M. |
| Long Text: | Both types of meridian indicators, AM and PM, were listed in a date specification. If one of the meridian indicator format masks, such as AM or A.M., is specified in the date, the other may not be specified. |
| Repair Text: | From Oracle doc: Use one meridian indicator format, with or without periods, consistently. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1815 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | BC/AD conflicts with use of B.C./A.D. |
| Long Text: | Both types of BC/AD indicators were listed in a date specification. If one of the BC/AD indicator format masks, such as BC or B.C., is specified in the date, the other may not be specified. |
| Repair Text: | From Oracle doc: Use one BC/AD indicator format, with or without periods, consistently. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | month may only be specified once |
| Long Text: | More than one month format code was listed in a date specification. Only one of the following month format codes may be specified in a date: MM, MON, MONTH. |
| Repair Text: | From Oracle doc: Remove all but one month format from the date specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1817 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | day of week may only be specified once |
| Long Text: | More than one day-of-the-week format code was listed in a date specification. Only one of the following day-of-the-week format codes may be specified in a date: D, DY, DAY. |
| Repair Text: | From Oracle doc: Remove all but one day-of-the-week format from the date specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1818 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | 'HH24' precludes use of meridian indicator |
| Long Text: | A date specification contained both a 24-hour time format code and a meridian indicator code. If hours are specified using the 24-hour time format (HH24), a meridian indicator, AM or PM, may not be specified. |
| Repair Text: | From Oracle doc: Remove the meridian indicator format code, AM/PM or A.M./P.M., or the 24-hour time format code, HH24, from the date specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1819 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | signed year precludes use of BC/AD |
| Long Text: | A date specification contained both a signed year and a B.C./A.D. indicator. If the year is specified with a sign, such as SYYYY, then B.C. or A.D. is implicit in the date and must not be entered. |
| Repair Text: | From Oracle doc: Remove the B.C./A.D. indicator from the date specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1820 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | format code cannot appear in date input format |
| Long Text: | A date specification contained an invalid format code. Only the following may be specified when entering a date: year, month, day, hours, minutes, seconds, Julian day, A.M./P.M. and B.C./A.D. |
| Repair Text: | From Oracle doc: Remove the invalid format code from the date specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1821 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | date format not recognized |
| Long Text: | A date specification contained an invalid format code. |
| Repair Text: | From Oracle doc: Check that only valid date format codes are specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1822 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | era format code is not valid with this calendar |
| Long Text: | An era format code, E or EE, was specified with a calendar which does not use era information. |
| Repair Text: | From Oracle doc: Retry the operation using a date format mask which does not contain era format codes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1830 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | date format picture ends before converting entire input %s |
| Long Text: | A valid date format picture included extra data. The first part of the format picture was converted into a valid date, but the remaining data was not required. |
| Repair Text: | From Oracle doc: Check the specifications for date format pictures and correct the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1831 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | year conflicts with Julian date |
| Long Text: | The wrong year was specified with a Julian day. If a year is specified with a Julian date, it must be the year in which the Julian date occurs. |
| Repair Text: | From Oracle doc: Remove the year value from the date specification or enter the correct year for the Julian date. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1832 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | day of year conflicts with Julian date |
| Long Text: | A Julian date was specified with the day of the year but the day did not correspond to the Julian date. If the day of the year is specified with a Julian date, it must be the same day as the Julian date. |
| Repair Text: | From Oracle doc: Remove the day of the year value from the date specification or enter the correct day for the Julian date. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1833 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | month conflicts with Julian date |
| Long Text: | The wrong month was specified with a Julian date. If a month is specified with a Julian date, it must be the month in which the Julian date occurs. |
| Repair Text: | From Oracle doc: Remove the month value from the date specification or enter the correct month for the Julian date. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1834 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | day of month conflicts with Julian date |
| Long Text: | A Julian date was specified with the day of the month, but the month day did not correspond to the Julian date. If the day of the month is specified with a Julian date, it must be the same day of the month as the Julian date. |
| Repair Text: | From Oracle doc: Remove the day of the month value from the date specification or enter the correct day of the month for the Julian date. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1835 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | day of week conflicts with Julian date |
| Long Text: | A Julian date was specified with the day of the week, but the weekday did not correspond to the Julian date. If the day of the week is specified with a Julian date, it must be the same day of the week as the Julian date. |
| Repair Text: | From Oracle doc: Remove the day of the week value from the date specification or enter the correct day of the week for the Julian date. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1836 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hour conflicts with seconds in day |
| Long Text: | The wrong hour was specified with seconds in the day. If an hour is specified with seconds past midnight (SSSSS), it must be the hour in which the seconds value falls. |
| Repair Text: | From Oracle doc: Remove the hour value from the date specification or specify the correct hour for the seconds past midnight. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1837 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | minutes of hour conflicts with seconds in day |
| Long Text: | A date specification contained both minutes of the hour and seconds in the day but the values did not correspond. If both minutes in the hour (MI) and seconds past midnight (SSSSS) are specified, the minutes value must be the minute in which the seconds value will occur. |
| Repair Text: | From Oracle doc: Remove the minutes value from the date specification or enter the correct minute value for the specified seconds value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1838 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | seconds of minute conflicts with seconds in day |
| Long Text: | A date specification contained both seconds of the minute and seconds in the day but the values did not correspond. If both types of seconds are specified, the seconds of the minute value (SS) must be the second in which the seconds past midnight value (SSSSS) will fall. |
| Repair Text: | From Oracle doc: Remove the seconds of the minute value from the date specification or enter a value that corresponds to the given seconds in the day. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1839 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | date not valid for month specified |
| Long Text: | The day of the month specified in the date is invalid for the given month. The day of the month (DD) must be between 1 and the number of days in the month. |
| Repair Text: | From Oracle doc: Enter a valid day of the month for the specified month. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1840 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input value not long enough for date format |
| Long Text: | The data to be converted to date format was incomplete; the date format picture was longer than the input data. |
| Repair Text: | From Oracle doc: Either add more input or shorten the date picture format, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1841 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | (full) year must be between -4713 and +9999, and not be 0 |
| Long Text: | A date specified a year that is not in the valid date range. A valid date is any date between January 1, 4712 B.C. and December 31, 9999 A.D. |
| Repair Text: | From Oracle doc: Enter a valid date value between 4712 B.C. and 9999 A.D. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1842 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | quarter must be between 1 and 4 |
| Long Text: | An invalid value was specified for the quarter of the year in a date. The quarter (Q) must be between 1 and 4. |
| Repair Text: | From Oracle doc: Enter a value for quarter between 1 and 4. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1843 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a valid month |
| Long Text: | A date specified an invalid month. Valid months are: January-December, for format code MONTH, and Jan-Dec, for format code MON. |
| Repair Text: | From Oracle doc: Enter a valid month value in the correct format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1844 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | week of year must be between 1 and 52 |
| Long Text: | An invalid value was specified for the week of the year in a date. Week of the year (WW) must be between 1 and 52. |
| Repair Text: | From Oracle doc: Enter a week of the year value between 1 and 52. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1845 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | week of month must be between 1 and 5 |
| Long Text: | An invalid value was specified for the week of the month in a date. Week of the month (W) must be between 1 and 5. |
| Repair Text: | From Oracle doc: Enter a week of the month value between 1 and 5. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1846 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a valid day of the week |
| Long Text: | A date specified an invalid day of the week. Valid days are: Monday-Sunday, for format code DAY Mon-Sun, for format code DY 1-7, for format code D |
| Repair Text: | From Oracle doc: Enter a valid day of the week value in the correct format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1847 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | day of month must be between 1 and last day of month |
| Long Text: | The day of the month listed in a date is invalid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month. |
| Repair Text: | From Oracle doc: Enter a valid day value for the specified month. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1848 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | day of year must be between 1 and 365 (366 for leap year) |
| Long Text: | An invalid day of the year was specified in a date. Day of the year (DDD) must be between 1 and 365 for a non-leap year or 1 and 366 for a leap year. |
| Repair Text: | From Oracle doc: Enter a day of the year value between 1 and 365 (or 366). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1849 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hour must be between 1 and 12 |
| Long Text: | An invalid hour was specified for a date using the 12-hour time format. If a 12-hour format code (HH or HH12) is used, the specified hour must be between 1 and 12. |
| Repair Text: | From Oracle doc: Enter an hour value between 1 and 12. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1850 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hour must be between 0 and 23 |
| Long Text: | An invalid hour was specified for a date using the 24-hour time format. If the 24-hour format code (HH24) is listed, the specified hour must be between 0 and 23. |
| Repair Text: | From Oracle doc: Enter an hour value between 0 and 23. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1851 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | minutes must be between 0 and 59 |
| Long Text: | An invalid minute value was specified in a date. Minutes must be between 0 and 59. |
| Repair Text: | From Oracle doc: Enter a minute value between 0 and 59. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1852 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | seconds must be between 0 and 59 |
| Long Text: | An invalid seconds value was specified in a date. Seconds must be between 0 and 59 if the seconds format code (SS) is used. |
| Repair Text: | From Oracle doc: Enter a seconds value between 0 and 59. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1853 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | seconds in day must be between 0 and 86399 |
| Long Text: | An invalid value for seconds in the day was specified in a date. Seconds must be between 0 and 86399 if the seconds past midnight format code (SSSSS) is used. |
| Repair Text: | From Oracle doc: Specify a seconds value between 0 and 86399. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1854 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | julian date must be between 1 and 5373484 |
| Long Text: | An invalid Julian date was entered. |
| Repair Text: | From Oracle doc: Enter a valid Julian date between 1 and 5373484. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1855 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | AM/A.M. or PM/P.M. required |
| Long Text: | A date specification contained a meridian indicator format code but a valid meridian indicator was not specified. If a meridian indicator code, A.M./P.M. or AM/PM, is included in a date format, the date must include a valid meridian indicator. |
| Repair Text: | From Oracle doc: Specify the meridian indicator in the correct format, A.M./AM or P.M./PM. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1856 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | BC/B.C. or AD/A.D. required |
| Long Text: | A date specification contained a BC/AD format code but a valid BC/AD indicator was not specified. If one of the BC/AD format codes, BC/AD or B.C./A.D., is specified in a date format, the date must include BC/B.C. or AD/A.D. |
| Repair Text: | From Oracle doc: Specify the BC/AD indicator in the date using the correct format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1857 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | not a valid time zone |
| Long Text: | An incorrect time zone code was specified for the NEW_TIME function. |
| Repair Text: | From Oracle doc: Correct the invalid time zone code, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1858 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a non-numeric character was found where a numeric was expected |
| Long Text: | The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model. |
| Repair Text: | From Oracle doc: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1859 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a non-alphabetic character was found where an alphabetic was expected |
| Long Text: | The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model. |
| Repair Text: | From Oracle doc: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1860 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | week of year must be between 1 and 53 |
| Long Text: | A week number outside the range 1 to 53 was specified. |
| Repair Text: | From Oracle doc: Use only a value within the valid range for the week number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1861 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | literal does not match format %s |
| Long Text: | Literals in the input must be the same length as literals in the format string (with the exception of leading white space). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra white space. |
| Repair Text: | From Oracle doc: Correct the format string to match the literal. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1862 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | the numeric value does not match the length of the format item |
| Long Text: | When the FX and FM format codes are specified for an input date, then the number of digits must be exactly the number specified by the format code. For example, 9 will not match the format specifier DD but 09 will. |
| Repair Text: | From Oracle doc: Correct the input date or turn off the FX or FM format specifier in the format string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1863 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the year is not supported for the current calendar |
| Long Text: | The year is not supported for the current calendar. |
| Repair Text: | From Oracle doc: Check the documentation to find out what years are supported for the current calendar. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1864 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the date is out of range for the current calendar |
| Long Text: | Your calendar does not extend to the specified date. |
| Repair Text: | From Oracle doc: Specify a date which is legal for this calendar. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1865 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a valid era |
| Long Text: | Era input does not match a known era. |
| Repair Text: | From Oracle doc: Provide a valid era on input. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1866 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the datetime class is invalid |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1867 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the interval is invalid |
| Long Text: | The character string you specified is not a valid interval. |
| Repair Text: | From Oracle doc: Specify a valid interval. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1868 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the leading precision of the interval is too small |
| Long Text: | The leading precision of the interval is too small to store the specified interval. |
| Repair Text: | From Oracle doc: Increase the leading precision of the interval or specify an interval with a smaller leading precision. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1869 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | Not an error. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1870 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the intervals or datetimes are not mutually comparable |
| Long Text: | The intervals or datetimes are not mutually comparable. |
| Repair Text: | From Oracle doc: Specify a pair of intervals or datetimes that are mutually comparable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1871 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the number of seconds must be less than 60 |
| Long Text: | The number of seconds specified was greater than 59. |
| Repair Text: | From Oracle doc: Specify a value for seconds that is 59 or smaller. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1872 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | Not an error. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1873 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the leading precision of the interval is too small |
| Long Text: | The leading precision of the interval is too small to store the specified interval. |
| Repair Text: | From Oracle doc: Increase the leading precision of the interval or specify an interval with a smaller leading precision. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1874 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | time zone hour must be between -12 and 13 |
| Long Text: | The time zone hour specified was not in the valid range. |
| Repair Text: | From Oracle doc: Specify a time zone hour between -12 and 13. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1875 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | time zone minute must be between -59 and 59 |
| Long Text: | The time zone minute specified was not in the valid range. |
| Repair Text: | From Oracle doc: Specify a time zone minute between -59 and 59. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1876 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | year must be at least -4713 |
| Long Text: | The specified year was not in range. |
| Repair Text: | From Oracle doc: Specify a year that is greater than or equal to -4713. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1877 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is too long for internal buffer |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1878 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified field not found in datetime or interval |
| Long Text: | The specified field was not found in the datetime or interval. |
| Repair Text: | From Oracle doc: Make sure that the specified field is in the datetime or interval. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1879 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the hh25 field must be between 0 and 24 |
| Long Text: | The specified hh25 field was not in the valid range. |
| Repair Text: | From Oracle doc: Specify an hh25 field between 0 and 24. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1880 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the fractional seconds must be between 0 and 999999999 |
| Long Text: | The specified fractional seconds were not in the valid range. |
| Repair Text: | From Oracle doc: Specify a value for fractional seconds between 0 and 999999999. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1890 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NLS error detected |
| Long Text: | An NLS error was detected. |
| Repair Text: | From Oracle doc: Look for additional error messages and take appropriate action. If there are no additional errors, call Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1891 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Datetime/Interval internal error |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1898 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | too many precision specifiers |
| Long Text: | While trying to truncate or round dates, extra data was found in the date format picture. |
| Repair Text: | From Oracle doc: Check the syntax of the date format picture and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1899 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad precision specifier |
| Long Text: | An invalid precision code was specified in a date. |
| Repair Text: | From Oracle doc: Enter a valid precision code in the date format. Valid precision types are: century, year, month, day, Julian date, hours, minutes, and seconds. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1900 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOGFILE keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1901 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ROLLBACK keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1902 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SEGMENT keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1903 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EVENTS keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1904 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DATAFILE keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1905 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | STORAGE keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1906 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | BACKUP keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1907 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TABLESPACE keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1908 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EXISTS keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1909 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REUSE keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1910 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TABLES keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1911 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CONTENTS keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1912 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ROW keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1913 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EXCLUSIVE keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1914 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid auditing option for sequence numbers |
| Long Text: | AUDIT or NOAUDIT on a sequence number specifies an auditing option that is not legal for sequence numbers. |
| Repair Text: | From Oracle doc: The following options may not be used for sequence numbers and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE, REFERENCES, EXECUTE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1915 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid auditing option for views |
| Long Text: | AUDIT or NOAUDIT on a view specifies an auditing option that is not legal for views. |
| Repair Text: | From Oracle doc: The following options may not be used for views and should be removed: ALTER, INDEX, REFERENCES, EXECUTE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1916 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected |
| Long Text: | An expected keyword was not used for DATAFILE/TEMPFILE clause |
| Repair Text: | From Oracle doc: Use correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1917 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user or role '%s' does not exist |
| Long Text: | There is not a user or role by that name. |
| Repair Text: | From Oracle doc: Re-specify the name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1918 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user '%s' does not exist |
| Long Text: | User does not exist in the system. |
| Repair Text: | From Oracle doc: Verify the user name is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1919 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | role '%s' does not exist |
| Long Text: | Role by that name does not exist. |
| Repair Text: | From Oracle doc: Verify you are using the correct role name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1920 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user name '%s' conflicts with another user or role name |
| Long Text: | There is already a user or role with that name. |
| Repair Text: | From Oracle doc: Specify a different user name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1921 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | role name '%s' conflicts with another user or role name |
| Long Text: | There is already a user or role with that name. |
| Repair Text: | From Oracle doc: Specify a different role name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1922 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CASCADE must be specified to drop '%s' |
| Long Text: | Cascade is required to remove this user from the system. The user own's object which will need to be dropped. |
| Repair Text: | From Oracle doc: Specify cascade. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1923 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CASCADE aborted, objects locked by another user |
| Long Text: | Cannot drop the user's objects; someone has them locked. |
| Repair Text: | From Oracle doc: Use the lock monitor to determine who has the objects locked. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1924 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | role '%s' not granted or does not exist |
| Long Text: | Set role can only be performed with roles granted directly to your account (for example, a sub-role cannot be enabled). |
| Repair Text: | From Oracle doc: Do not try to set the role. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1925 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum of %s enabled roles exceeded |
| Long Text: | The initialization parameter MAX_ENABLED_ROLES has been exceeded. |
| Repair Text: | From Oracle doc: Increase MAX_ENABLED_ROLES and warm start the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1926 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot GRANT to a role WITH GRANT OPTION |
| Long Text: | Role cannot have a privilege with the grant option. |
| Repair Text: | From Oracle doc: Perform the grant without the grant option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1927 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot REVOKE privileges you did not grant |
| Long Text: | You can only revoke privileges you granted. |
| Repair Text: | From Oracle doc: Do not revoke these privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1928 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GRANT option not granted for all privileges |
| Long Text: | In order to grant a privilege, you must first have the privilege with the grant option. |
| Repair Text: | From Oracle doc: Obtain the privilege with the grant option and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1929 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no privileges to GRANT |
| Long Text: | "ALL" was specified but the user does not have any privileges with the grant option. |
| Repair Text: | From Oracle doc: Do not grant privileges on that object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1930 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | auditing the object is not supported |
| Long Text: | AUDIT or NOAUDIT was specified for an object that cannot be audited. |
| Repair Text: | From Oracle doc: Do not attempt to AUDIT the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1931 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot grant %s to a role |
| Long Text: | UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA or SYSOPER privilege cannot be granted to a role. |
| Repair Text: | From Oracle doc: Grant privilege directly to the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1932 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ADMIN option not granted for role '%s' |
| Long Text: | The operation requires the ADMIN option on the role. |
| Repair Text: | From Oracle doc: Obtain the grant option and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1933 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a stored object using privileges from a role |
| Long Text: | An attempt was made to create a stored object using privileges from a role. Stored objects cannot use privileges from roles. |
| Repair Text: | From Oracle doc: Grant the privileges required to the user directly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1934 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | circular role grant detected |
| Long Text: | Roles cannot be granted circularly. Also, a role cannot be granted to itself. |
| Repair Text: | From Oracle doc: Do not perform the grant. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1935 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing user or role name |
| Long Text: | A user or role name was expected. |
| Repair Text: | From Oracle doc: Specify a user or role name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1936 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify owner when creating users or roles |
| Long Text: | Users and roles do not have owners. |
| Repair Text: | From Oracle doc: Do not specify an owner. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1937 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid role name |
| Long Text: | A valid role name was expected. |
| Repair Text: | From Oracle doc: Specify a valid role name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1938 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IDENTIFIED BY must be specified for CREATE USER |
| Long Text: | Cannot create a user without specifying a password or IDENTIFIED EXTERNALLY. |
| Repair Text: | From Oracle doc: Specify one of the password clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1939 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only the ADMIN OPTION can be specified |
| Long Text: | System privileges and Roles can only be granted with the ADMIN option. The grant option cannot be used with these privileges. |
| Repair Text: | From Oracle doc: Specify the ADMIN option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1940 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop a user that is currently connected |
| Long Text: | Attempt was made to drop a user that is currently logged in. |
| Repair Text: | From Oracle doc: Make sure user is logged off, then repeat command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1941 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SEQUENCE keyword expected |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1942 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IDENTIFIED BY and EXTERNALLY cannot both be specified |
| Long Text: | A user cannot be specified to have and not have a password. |
| Repair Text: | From Oracle doc: Specify only one of the options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1943 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IDENTIFIED BY already specified |
| Long Text: | The IDENTIFIED clause has been given twice. |
| Repair Text: | From Oracle doc: Use only one IDENTIFIED BY clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1944 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IDENTIFIED EXTERNALLY already specified |
| Long Text: | The IDENTIFIED EXTERNALLY clause has been given twice. |
| Repair Text: | From Oracle doc: Use only one IDENTIFIED clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1945 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DEFAULT ROLE[S] already specified |
| Long Text: | The DEFAULT ROLES clause has been given twice. |
| Repair Text: | From Oracle doc: Use only one DEFAULT ROLE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1946 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DEFAULT TABLESPACE already specified |
| Long Text: | The DEFAULT TABLESPACE clause has been given twice. |
| Repair Text: | From Oracle doc: Use only one DEFAULT TABLESPACE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1947 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TEMPORARY TABLESPACE already specified |
| Long Text: | The TEMPORARY TABLESPACE clause has been given twice. |
| Repair Text: | From Oracle doc: Use only one TEMPORARY TABLESPACE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1949 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ROLE keyword expected |
| Long Text: | The ROLE keyword is required here. |
| Repair Text: | From Oracle doc: Specify the ROLE keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1950 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no privileges on tablespace '%s' |
| Long Text: | User does not have privileges to allocate an extent in the specified tablespace. |
| Repair Text: | From Oracle doc: Grant the user the appropriate system privileges or grant the user space resource on the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1951 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ROLE '%s' not granted to '%s' |
| Long Text: | The role you tried to revoke was not granted to the user. |
| Repair Text: | From Oracle doc: Do not try to revoke a privilege which is not granted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1952 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system privileges not granted to '%s' |
| Long Text: | A system privilege you tried to revoke was not granted to the user. |
| Repair Text: | From Oracle doc: Make sure the privileges you are trying to revoke are granted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1953 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | command no longer valid, see ALTER USER |
| Long Text: | The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to perform the functionality. |
| Repair Text: | From Oracle doc: Use the ALTER USER command instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1954 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DEFAULT ROLE clause not valid for CREATE USER |
| Long Text: | Default roles cannot be specified for create user. |
| Repair Text: | From Oracle doc: Grant and alter the user's default roles after creating the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1955 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DEFAULT ROLE '%s' not granted to user |
| Long Text: | The user being altered does not have the specified role granted directly to the user. Note, sub-roles cannot be used in the DEFAULT ROLE clause. |
| Repair Text: | From Oracle doc: Grant the role to the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1956 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid command when OS_ROLES are being used |
| Long Text: | This command cannot be used when the initialization parameter OS_ROLES is TRUE. |
| Repair Text: | From Oracle doc: Grant the role to the user in the operating system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1957 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Keyword MIN or MAX expected, not found |
| Long Text: | The keyword MIN or MAX was expected as an argument. |
| Repair Text: | From Oracle doc: Enter the keyword MIN or MAX and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1958 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must supply an integer for the LAYER option |
| Long Text: | An item other than an integer was entered for the LAYER option. |
| Repair Text: | From Oracle doc: Enter an integer for the LAYER option and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1959 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must supply an integer for the OPCODE option |
| Long Text: | An item other than an integer was entered for the OPCODE option. The value in ALTER SYSTEM DUMP ... OPCODE value must be an integer. |
| Repair Text: | From Oracle doc: Enter an integer for the OPCODE option and retry the operation. For more information on the OPCODE option, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1960 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid dump logfile option |
| Long Text: | An invalid option was entered for the ALTER SYSTEM DUMP LOGFILE option command. |
| Repair Text: | From Oracle doc: For a list of valid options for DUMP LOGFILE, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1961 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid dump option |
| Long Text: | An invalid option was entered for the ALTER SYSTEM DUMP command. |
| Repair Text: | From Oracle doc: Enter a valid option for ALTER SYSTEM DUMP. Examples of valid options are LOGFILE and UNDO. For more information on the DUMP option, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1962 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must specify a file number or log sequence number |
| Long Text: | An invalid file number or log sequence number was specified. |
| Repair Text: | From Oracle doc: Enter a valid file number or log sequence number and retry the operation. For more information on valid file and log sequence numbers, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1963 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must specify a block number |
| Long Text: | An invalid block number was specified. |
| Repair Text: | From Oracle doc: Enter a valid block number and retry the operation. For more information on valid block numbers, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1964 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must specify a time for the TIME option |
| Long Text: | A value was entered for the TIME option that could not be interpreted as a date. |
| Repair Text: | From Oracle doc: Enter a valid date. For more information on the TIME option, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1965 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must specify a PERIOD |
| Long Text: | A period is missing between the file number and the block number. |
| Repair Text: | From Oracle doc: Enter a period between the file number and the block number, then retry the operation. For more information on file numbers and block numbers, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1967 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for CREATE CONTROLFILE |
| Long Text: | An invalid CREATE CONTROLFILE option is present. |
| Repair Text: | From Oracle doc: Specify only valid CREATE CONTROLFILE options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1968 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Only specify RESETLOGS or NORESETLOGS once |
| Long Text: | The keyword RESETLOGS or NORESETLOGS has appeared more than once. |
| Repair Text: | From Oracle doc: Be sure to specify RESETLOGS or NORESETLOGS exactly once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1969 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | You must specify RESETLOGS or NORESETLOGS |
| Long Text: | Missing a RESETLOGS or a NORESETLOGS. |
| Repair Text: | From Oracle doc: Be sure to specify RESETLOGS or NORESETLOGS exactly once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1970 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | You must specify a database name for CREATE CONTROLFILE |
| Long Text: | Missing a database name. |
| Repair Text: | From Oracle doc: Retype CREATE CONTROLFILE command with the DATABASE keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1971 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Illegal ALTER TRACING option |
| Long Text: | An invalid ALTER TRACING option is present. |
| Repair Text: | From Oracle doc: Specify only valid ALTER TRACING options. Examples of valid options are ENABLE and DISABLE. For more information, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1972 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must specify a %s for ALTER TRACING ENABLE or DISABLE |
| Long Text: | Something other than a valid identifier was specified for ALTER TRACING ENABLE or DISABLE. |
| Repair Text: | From Oracle doc: Specify a valid identifier for ALTER TRACING ENABLE or DISABLE and retry the operation. For more information on valid identifiers, see the Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1973 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Missing change number |
| Long Text: | Keyword CHANGE found but change number not specified. |
| Repair Text: | From Oracle doc: Fix the command line and resubmit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1974 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Illegal archive option |
| Long Text: | An invalid option to the ALTER SYSTEM ARCHIVE command was specified. |
| Repair Text: | From Oracle doc: Check the syntax of the command and retry it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1975 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Illegal character in change number %s |
| Long Text: | An invalid change number was supplied. |
| Repair Text: | From Oracle doc: Resubmit the command with a valid change number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1976 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Missing change number |
| Long Text: | A change number was required, but not supplied. |
| Repair Text: | From Oracle doc: Check the syntax of the command, supply a change number where needed, then retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1977 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Missing thread number |
| Long Text: | Keyword THREAD found but thread number not specified. |
| Repair Text: | From Oracle doc: Fix the command line and resubmit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1978 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Missing sequence number |
| Long Text: | Keyword SEQUENCE found but sequence number not specified. |
| Repair Text: | From Oracle doc: Fix the command line and resubmit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1979 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid password for role '%s' |
| Long Text: | An attempt was made to enable a role without giving the proper password. |
| Repair Text: | From Oracle doc: Use the IDENTIFIED BY clause in SET ROLE to specify the correct password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1980 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error during OS ROLE initialization |
| Long Text: | An operating system error occurred while loading a users OS ROLES. |
| Repair Text: | From Oracle doc: Check the operating system error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1981 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CASCADE CONSTRAINTS must be specified to perform this revoke |
| Long Text: | During this revoke some foreign key constraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified. |
| Repair Text: | From Oracle doc: Remove the constraints or specify CASCADE CONSTRAINTS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1982 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid auditing option for tables |
| Long Text: | AUDIT or NOAUDIT on a table specifies an auditing option that is not legal for tables. |
| Repair Text: | From Oracle doc: The following options may not be used for tables and should be removed: REFERENCES, EXECUTE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1983 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid auditing option for DEFAULT |
| Long Text: | AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for DEFAULT. |
| Repair Text: | From Oracle doc: The following options may not be used for DEFAULT and should be removed: REFERENCES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1984 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid auditing option for procedures/packages/functions |
| Long Text: | AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for procedures, packages, or functions. |
| Repair Text: | From Oracle doc: The following options may not be used for procedures, packages, and functions and should be removed: all but EXECUTE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1985 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create user as LICENSE_MAX_USERS parameter exceeded |
| Long Text: | Maximum users in the database license limit exceeded. |
| Repair Text: | From Oracle doc: Increase license limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1986 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid option for OPTIMIZER_GOAL |
| Long Text: | An invalid OPTIMIZER_GOAL option is present. |
| Repair Text: | From Oracle doc: Check the syntax for OPTIMIZER_GOAL, specify a valid option and re-execute the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1987 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | client os username is too long |
| Long Text: | A client's operating system username is too long for the operating system logon to succeed. |
| Repair Text: | From Oracle doc: Use a shorter operating system username. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1988 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote os logon is not allowed |
| Long Text: | Remote operating system login attempted when not allowed. |
| Repair Text: | From Oracle doc: Use a local client, or use the REMOTE_OS_AUTHENT system parameter to turn on remote operating system logon. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1989 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | role '%s' not authorized by operating system |
| Long Text: | The operating system role does not exist, is not granted to you, or you did not provide the correct password. |
| Repair Text: | From Oracle doc: Re-attempt the SET ROLE with a valid operating system role and password, if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1990 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error opening password file '%s' |
| Long Text: | An attempt to open the specified password file failed because of one of the following errors: An operating system error occurred. ORAPWD is already running, so the password file is locked. The environment variables ORA_sid_PWFILE and ORA_PWFILE are not set. |
| Repair Text: | From Oracle doc: Check for the above causes and correct as necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1991 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid password file '%s' |
| Long Text: | The specified password file name is invalid. |
| Repair Text: | From Oracle doc: Specify a correct password file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1992 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error closing password file '%s' |
| Long Text: | The password file could not be closed because of an operating system error or because an authentication action failed. |
| Repair Text: | From Oracle doc: Check for the above causes and correct as necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1993 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error writing password file '%s' |
| Long Text: | The password file could not be written to because of an operating system error or because an authentication action failed. |
| Repair Text: | From Oracle doc: Check for the above causes and correct as necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1994 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GRANT failed: cannot add users to shared password file |
| Long Text: | A grant failed because a user could not be added to the password file. This is because the value of the REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED. |
| Repair Text: | From Oracle doc: To add a user to the password file, shut down the database, change the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE, and restart the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1995 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error reading password file '%s' |
| Long Text: | An operating system error occurred when trying to read the password file. |
| Repair Text: | From Oracle doc: Fix the operating system error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1996 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GRANT failed: password file '%s' is full |
| Long Text: | The grant failed when a user could not be added to the password file, because all available slots in it were used already. |
| Repair Text: | From Oracle doc: Either create a larger password file or free up slots in the password file by revoking the SYSOPER and SYSDBA privileges from some of the remote users. You can determine which remote users are valid and their privileges by issuing the following query in SQL*DBA: SELECT * FROM V$REMOTE_USERS; |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1997 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GRANT failed: user '%s' is identified externally |
| Long Text: | You cannot grant the SYSOPER or SYSDBA privilege to a user created with the IDENTIFIED EXTERNALLY clause. |
| Repair Text: | From Oracle doc: If you wish to grant the user the SYSOPER or SYSDBA privileges, drop and re-create the user without the IDENTIFIED EXTERNALLY clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1998 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REVOKE failed: user SYS always has SYSOPER and SYSDBA |
| Long Text: | You attempted to revoke one of the necessary privileges, SYSOPER or SYSDBA, from user SYS. These privileges cannot be revoked. |
| Repair Text: | From Oracle doc: Do not attempt this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-1999 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | password file mode has changed from '%s' to '%s' |
| Long Text: | Another instance has started with the FORCE_PASSWORD_FILEMODE initialization parameter, which is incompatible with the startup mode of your instance. |
| Repair Text: | From Oracle doc: Shut down your instance and start up later when the password file changes are completed for the other instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing %s keyword |
| Long Text: | The statement entered requires the missing keyword. |
| Repair Text: | From Oracle doc: Use the specified keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user SYS is not permitted to create indexes with freelist groups |
| Long Text: | An attempt was made to create an index while running with SYS authorization. |
| Repair Text: | From Oracle doc: Indexes cannot be created with SYS authorization. Either do not create the index or switch to USER authorization. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while writing to audit trail |
| Long Text: | The auditing facility is unable to write to the AUDIT_TRAIL table. If this error occurs, SQL statements that are currently being audited may also fail. This error will occur if the SYSTEM tablespace runs out of disk space. |
| Repair Text: | From Oracle doc: Add space to the SYSTEM tablespace or delete rows from the AUDIT_TRAIL table. If these operations fail or do not eliminate the problem, shut down and restart Oracle with auditing disabled. This is done by setting the initialization parameter AUDIT_TRAIL to FALSE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid USERENV parameter |
| Long Text: | An invalid parameter was specified for the USERENV function. |
| Repair Text: | From Oracle doc: Specify one of the allowable parameters TERMINAL, SESSIONID, ENTRYID, or NLS_LANG. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | security violation |
| Long Text: | A user is attempting to perform an operation without the proper permission, and this fact is being recorded in the AUDIT_TRAIL table. This message only appears in the AUDIT_TRAIL table's return code column. |
| Repair Text: | From Oracle doc: For auditing information only; no action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | implicit (-1) length not valid for this bind or define datatype |
| Long Text: | A negative length for the define variable was passed to a define function. |
| Repair Text: | From Oracle doc: An explicit, non-negative, length parameter must be passed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid packed decimal format %s |
| Long Text: | A packed decimal datatype was passed to a bind or define function, and the format string parameter was either not present or invalid. |
| Repair Text: | From Oracle doc: A valid format string parameter must be passed for a packed decimal variable. Check the programming manual for the definition of a packed decimal format string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can't use ALLOCATE or DEALLOCATE options with REBUILD |
| Long Text: | Allocate or deallocate storage and rebuild index are not compatible. |
| Repair Text: | From Oracle doc: Choose one or the other. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-zero scale specified for nonnumeric column |
| Long Text: | A scale factor was specified for a bind or define of a non-numeric variable. |
| Repair Text: | From Oracle doc: Set the scale factor to zero, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the size specified for a file must not be zero |
| Long Text: | A value of zero was specified in a SIZE or RESIZE clause of a file specification. |
| Repair Text: | From Oracle doc: Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing host connect %s |
| Long Text: | A quoted character string does not follow the keyword USING in the USING clause of a CREATE DATABASE LINK statement. |
| Repair Text: | From Oracle doc: Specify the host connect string, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate database link name |
| Long Text: | The database link name specified in a CREATE DATABASE LINK statement already exists. |
| Repair Text: | From Oracle doc: Either specify a new name or drop the existing link. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing USING keyword |
| Long Text: | The keyword USING does not follow the CONNECT TO clause in a CREATE DATABASE LINK statement. |
| Repair Text: | From Oracle doc: Specify the USING clause after the CONNECT TO clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing CONNECT keyword |
| Long Text: | The keyword CONNECT does not follow the database link name in a CREATE DATABASE LINK statement. |
| Repair Text: | From Oracle doc: Specify the CONNECT clause after the database link name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc. |
| Long Text: | An attempt was made to SELECT... FOR UPDATE from a view whose defining SELECT statement uses at least one of the following constructs in its outer block: outer join, GROUP BY clause, aggregate functions, SELECT DISTINCT, CONNECT BY clause, or set operation, UNION, INTERSECT, or MINUS. |
| Repair Text: | From Oracle doc: Do not use SELECT... FOR UPDATE on this view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot select FOR UPDATE from remote table |
| Long Text: | An attempt was made to SELECT... FOR UPDATE from a table in a remote database. |
| Repair Text: | From Oracle doc: It is not currently possible to SELECT... FOR UPDATE from a table in a remote database. Instead, log in or connect directly to the remote database before entering a SELECT... FOR UPDATE on its tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use a subquery in a START WITH on a remote database |
| Long Text: | An attempt was made to use a subquery in a START WITH clause. Such a subquery is not currently permitted if the table in the FROM clause of the tree query is in a remote database. |
| Repair Text: | From Oracle doc: It is necessary to connect directly to the remote database before using a subquery in the START WITH clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | integer value required |
| Long Text: | The specified value must be an integer. |
| Repair Text: | From Oracle doc: Specify an appropriate integer value, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link of same name has an open connection |
| Long Text: | The user is currently connected to a PUBLIC database link with the same name as the database link name specified in a CREATE or DROP DATABASE LINK statement. |
| Repair Text: | From Oracle doc: Close the cursors that use the PUBLIC database link. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection description for remote database not found |
| Long Text: | An attempt was made to connect or log in to a remote database using a connection description that could not be found. |
| Repair Text: | From Oracle doc: Specify an existing database link. Query the data dictionary to see all existing database links. See your operating system-specific Net8 documentation for valid connection descriptors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many database links in use |
| Long Text: | The current session has exceeded the INIT.ORA OPEN_LINKS maximum. |
| Repair Text: | From Oracle doc: Increase the OPEN_LINKS limit, or free up some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DDL operations are not allowed on a remote database |
| Long Text: | An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE tablename@remotedbname...". |
| Repair Text: | From Oracle doc: To alter the remote database structure, you must connect to the remote database with the appropriate privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote statement has unoptimized view with remote object |
| Long Text: | The local view is unoptimized and contains references to objects at the remote database and the statement must be executed at the remote database. |
| Repair Text: | From Oracle doc: Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | START WITH or CONNECT BY predicate cannot be evaluated by remote data base |
| Long Text: | The statement contains a tree query on a remote database, and the tree query's START WITH or CONNECT BY predicate contains a term that cannot be evaluated at the remote database. Such terms include calls to user functions, calls to USERENV, and references to ROWID. |
| Repair Text: | From Oracle doc: Remove the disallowed term, directly connect, or log on to the remote database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link not found |
| Long Text: | Database link to be dropped is not found in dictionary. |
| Repair Text: | From Oracle doc: Correct the database link name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | all tables in the SQL statement must be at the remote database |
| Long Text: | A SQL statement referenced tables from multiple databases, and one or more of the remote databases are not Oracle Servers. |
| Repair Text: | From Oracle doc: Remote updates can be performed only if all databases in the SQL statement are Oracle Servers. Update the earlier version databases in a separate statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing LINK keyword |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | multi-row UPDATE of LONG column is not supported |
| Long Text: | A bind variable with length greater than 4000 bytes is being used to update a column, and the update statement updates more than one row. |
| Repair Text: | From Oracle doc: You may only update a single row with such a bind variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fetching an exact number of rows is not supported by the server |
| Long Text: | The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side. |
| Repair Text: | From Oracle doc: Connect to a valid server or do not use an exact fetch. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing FILE keyword |
| Long Text: | A keyword is missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can only select from fixed tables/views |
| Long Text: | An attempt is being made to perform an operation other than a retrieval from a fixed table/view. |
| Repair Text: | From Oracle doc: You may only select rows from fixed tables/views. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no ROWID for fixed tables or for index-organized tables |
| Long Text: | An attempt is being made to access ROWID from a fixed table or from a index-organized table. |
| Repair Text: | From Oracle doc: Do not access ROWID from a fixed table or from a index-organized table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | clustered tables cannot be used before the cluster index is built |
| Long Text: | User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created. |
| Repair Text: | From Oracle doc: Create the cluster index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2033 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | a cluster index for this cluster already exists |
| Long Text: | A cluster index already exists for the cluster. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2034 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | speed bind not permitted |
| Long Text: | Speed bind not allowed with supplied bind variables. Trapped internally by the system. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal bundled operation combination |
| Long Text: | User requested that the UPI bundled execution call perform an illegal combination of operations. |
| Repair Text: | From Oracle doc: Use a legal combination of operations and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many variables to describe with automatic cursor open |
| Long Text: | UPI-bundled execution call tried to perform automatic cursor open and close on a describe operation. There were too many SELECT list items or bind variables to do this. |
| Repair Text: | From Oracle doc: Open and close cursor explicitly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | uninitialized speed bind storage |
| Long Text: | An attempt was made to perform a speed-execution call on a SQL statement containing host variables without first performing a speed-bind call. |
| Repair Text: | From Oracle doc: Perform a speed-bind call before performing a speed-execution call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | define is not allowed for array type |
| Long Text: | A user attempted to define a select list variable of type "array". Arrays may serve only as host bind variables. |
| Repair Text: | From Oracle doc: Correct the offending code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bind by value is not allowed for array type |
| Long Text: | User attempted to bind an array host variable by value. Arrays may be bound only by reference. |
| Repair Text: | From Oracle doc: Correct the offending code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote database %s does not support two-phase commit |
| Long Text: | A distributed update of more than one database was attempted, but the named database does not support the prepare phase of the two-phase commit, as determined by its logon transaction traits. The transaction was rolled back. |
| Repair Text: | From Oracle doc: Do not attempt to update the named database, unless it is the only database updated in the transaction. Distributed updates of more than one database in a single transaction can be performed only if all databases support the two-phase commit mechanism. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | client database did not begin a transaction |
| Long Text: | An update occurred at a coordinated database without the coordinator beginning a distributed transaction. This may happen if a stored procedure commits and then performs updates, and the stored procedure is invoked remotely. It could also happen if an external transaction monitor violates the XA protocol. |
| Repair Text: | From Oracle doc: If the cause is the former, check that any commit is not followed by an update. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many distributed transactions |
| Long Text: | The distributed transaction table is full because too many distributed transactions are active. |
| Repair Text: | From Oracle doc: Increase the DISTRIBUTED_TRANSACTIONS parameter in the initialization parameter file, shut down and restart Oracle, or run fewer transactions. If it is certain there are not too many concurrent distributed transactions, this may be an internal error. In this case, contact Oracle Customer Support. Shutting down and restarting the instance could be a workaround. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must end current transaction before executing %s |
| Long Text: | A transaction is in progress and one of the following commands is issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode. |
| Repair Text: | From Oracle doc: COMMIT or ROLLBACK the current transaction and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction manager login denied: transaction in progress |
| Long Text: | A remote transaction manager tried to log in while a distributed transaction is in progress. A protocol error occurred in the remote transaction manager. |
| Repair Text: | From Oracle doc: End the current transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many local sessions participating in global transaction |
| Long Text: | There are too many sessions at this site to accommodate this transaction. |
| Repair Text: | From Oracle doc: Use an existing database link so that another session need not be created at the remote site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2046 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | distributed transaction already begun |
| Long Text: | This is an internal error not normally encountered. A server session received a BEGIN_TRAN remote procedure call before finishing with a previous distributed transaction. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2047 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot join the distributed transaction in progress |
| Long Text: | This can happen only when attempting to update an Oracle Version 6 and an Oracle7 database in the same transaction, because either A transaction is in progress against a remote database that does not support two-phase commit. Updates are pending and an attempt was made to update a different database that does not support two-phase commit. |
| Repair Text: | From Oracle doc: Complete the current transaction before attempting the action that caused the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2048 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to begin distributed transaction without logging on |
| Long Text: | The client program did not issue a distributed transaction login. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2049 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | timeout: distributed transaction waiting for lock |
| Long Text: | Exceeded INIT.ORA DISTRIBUTED_LOCK_TIMEOUT seconds waiting for lock. |
| Repair Text: | From Oracle doc: Treat as a deadlock. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2050 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction %s rolled back, some remote DBs may be in-doubt |
| Long Text: | Network or remote failure during a two-phase commit. |
| Repair Text: | From Oracle doc: Notify operations; remote databases will automatically re-sync when the failure is repaired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2051 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | another session in same transaction failed |
| Long Text: | A session at the same site with same global transaction ID failed. |
| Repair Text: | From Oracle doc: No action necessary; the transaction is automatically recovered. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote transaction failure at %s |
| Long Text: | There was some error in a remote transaction at the named database link. |
| Repair Text: | From Oracle doc: More descriptive messages will follow. Correct the problem specified in the following messages and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction %s committed, some remote DBs may be in-doubt |
| Long Text: | There was a network failure or a remote failure during the two-phase commit. |
| Repair Text: | From Oracle doc: Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction %s in-doubt |
| Long Text: | There was a network failure or a remote failure in the two-phase commit. |
| Repair Text: | From Oracle doc: Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired. Monitor the DBA_2PC_PENDING table for the outcome and resubmit the transaction, if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2055 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | distributed update operation failed; rollback required |
| Long Text: | A failure during a distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent with others, the transaction must roll back to a savepoint or roll back entirely. |
| Repair Text: | From Oracle doc: Roll back to a savepoint or roll back the entire transaction and resubmit the rolled-back statements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2056 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | 2PC: %s: bad two-phase command number %s from %s |
| Long Text: | There was a two-phase commit protocol error. |
| Repair Text: | From Oracle doc: The transaction may automatically recover. Monitor the DBA_2PC_PENDING table to determine the resolution. Enter the transaction again, if necessary. Contact Oracle Customer Support if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2057 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | 2PC: %s: bad two-phase recovery state number %s from %s |
| Long Text: | An internal error in the two-phase recovery protocol occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2058 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no prepared transaction found with ID %s |
| Long Text: | No transaction with LOCAL_TRAN_ID or GLOBAL_TRAN_ID found in the PENDING_TRANS$ table in prepared state. |
| Repair Text: | From Oracle doc: Check the PENDING_TRANS$ table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2059 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORA-2PC-CRASH-TEST-%s in commit comment |
| Long Text: | This is a special comment used to test the two-phase commit. |
| Repair Text: | From Oracle doc: Do not use this special comment (string a number 1-10). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | select for update specified a join of distributed tables |
| Long Text: | An attempt was made to join tables in different remote databases in a SELECT... FOR UPDATE statement. |
| Repair Text: | From Oracle doc: Joined tables in a SELECT statement with the FOR UPDATE clause must reside at the same database. Simplify the SELECT... FOR UPDATE statement so that it joins only tables in the same database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | lock table specified list of distributed tables |
| Long Text: | Tables in a LOCK TABLE statement must reside at the same database. |
| Repair Text: | From Oracle doc: Issue multiple LOCK TABLE commands. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2062 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | distributed recovery received DBID %s, expected %s |
| Long Text: | A database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different database mounted. |
| Repair Text: | From Oracle doc: Restore the link definition or the remote database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2063 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | preceding string%s from string%s |
| Long Text: | An Oracle error was received from a remote database link. |
| Repair Text: | From Oracle doc: Refer to the preceding error message(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2064 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | distributed operation not supported |
| Long Text: | One of the following unsupported operations was attempted: Array execute of a remote update with a subquery that references a database link, or An update of a long column with bind variable and an update of a second column with a subquery that both references a database link and a bind variable, or A commit is issued in a coordinated session from an RPC with OUT parameters. |
| Repair Text: | From Oracle doc: Simplify the remote update statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2065 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal option for ALTER SYSTEM |
| Long Text: | The option specified for ALTER SYSTEM is not supported. |
| Repair Text: | From Oracle doc: Refer to the Oracle8i SQL Reference for information about options supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2066 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid MTS_DISPATCHERS text |
| Long Text: | A character string literal was expected, but not found, following ALTER SYSTEM SET MTS_DISPATCHERS. |
| Repair Text: | From Oracle doc: Place the string literal containing the dispatcher's specification after ALTER SYSTEM SET MTS_DISPATCHERS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2067 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction or savepoint rollback required |
| Long Text: | A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed. |
| Repair Text: | From Oracle doc: Roll back to a previous savepoint or roll back the transaction and resubmit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2068 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | following severe error from string%s |
| Long Text: | A severe error (disconnect, fatal Oracle error) was received from the indicated database link. See following error text. |
| Repair Text: | From Oracle doc: Contact the remote system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2069 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | global_names parameter must be set to TRUE for this operation |
| Long Text: | A remote mapping of the statement is required but cannot be achieved because GLOBAL_NAMES should be set to TRUE for it to be achieved. |
| Repair Text: | From Oracle doc: Issue ALTER SESSION SET GLOBAL_NAMES = TRUE if possible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2070 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database string%s does not support %s in this context |
| Long Text: | The remote database does not support the named capability in the context in which it is used. |
| Repair Text: | From Oracle doc: Simplify the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error initializing capabilities for remote database %s |
| Long Text: | Could not load a remote-specified capability table. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support for the remote SQL*Connect product. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2072 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | distributed database network protocol mismatch |
| Long Text: | This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example. |
| Repair Text: | From Oracle doc: Upgrade the older release. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2073 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence numbers not supported in remote updates |
| Long Text: | Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables. |
| Repair Text: | From Oracle doc: Perform the operation without specifying a sequence number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot %s in a distributed transaction |
| Long Text: | A commit or rollback was attempted from session other than the parent of a distributed transaction. |
| Repair Text: | From Oracle doc: Only commit or roll back from the parent session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2075 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | another instance changed state of transaction %s |
| Long Text: | A commit force or rollback force was issued from a session in another instance. |
| Repair Text: | From Oracle doc: Check if another Oracle instance is performing recovery of pending transactions. Query DBA_2PC_PENDING to determine the new state of the transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2076 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence not co-located with updated table or long column |
| Long Text: | All referenced sequences must be located on the same node as the updated table or the long column. |
| Repair Text: | From Oracle doc: Correct the problem and then reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2077 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | selects of long columns must be from co-located tables |
| Long Text: | All tables returning values of long columns in a SELECT statement must be located at the same node. |
| Repair Text: | From Oracle doc: Correct the problem, then reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid setting for ALTER SYSTEM FIXED_DATE |
| Long Text: | An invalid value was used. |
| Repair Text: | From Oracle doc: Use a correct value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2079 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no new sessions may join a committing distributed transaction |
| Long Text: | A call to UPI2BG was issued in a session for a transaction that has begun to commit in a different branch; that is, a call to UPI2EN was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2080 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link is in use |
| Long Text: | A transaction is active or a cursor is open on the database link given in the ALTER SESSION CLOSE DATABASE LINK link command. |
| Repair Text: | From Oracle doc: Commit or roll back, and close all cursors |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2081 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link is not open |
| Long Text: | An attempt was made to use a database link that is not currently open. |
| Repair Text: | From Oracle doc: Resolve network problems or contact the remote database administrator to determine if the remote database's problem has been fixed. Contact the local database administrator to determine if network problems have been resolved. Wait until the link is open and try the operation again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a loopback database link must have a connection qualifier |
| Long Text: | An attempt was made to create a database link with the same name as the current database. |
| Repair Text: | From Oracle doc: This database link needs a trailing qualifier to make the name unique. These qualifiers are operating system-specific. See your operating system-specific Oracle documentation for more information about creating database links. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2083 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database name has illegal character '%s' |
| Long Text: | The database name supplied contains an invalid character. For example, there can be no periods, semicolons, single quotes, double quotes, blanks, or non-printable characters in the database name. See the Oracle8i Administrator's Guide for naming rules. |
| Repair Text: | From Oracle doc: Specify a valid database name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database name is missing a component |
| Long Text: | The complete database name was not provided. |
| Repair Text: | From Oracle doc: Specify the full database name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2085 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link %s connects to %s |
| Long Text: | The database link attempted to connect to a database with a different name. The name of the database link must be the same name as the name of the database. |
| Repair Text: | From Oracle doc: Create a database link with the same name as the database to which it connects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2086 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database (link) name is too long |
| Long Text: | The name of the database or database link is too long. Database and database link names can be no longer than 128 characters. |
| Repair Text: | From Oracle doc: Specify the correct database or database link name or specify a name with fewer characters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2087 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object locked by another process in same transaction |
| Long Text: | A database link is being used in the parallel server environment that loops back to the same instance. One session is trying to convert a lock that was obtained by the other session. |
| Repair Text: | From Oracle doc: Get the more restrictive lock first. For example, if session 1 gets a share lock and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or use the same session to access the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2088 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | distributed database option not installed |
| Long Text: | The distributed database option is not installed at this site, so the requested operation is not possible. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support about obtaining the distributed database option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2089 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | COMMIT is not allowed in a subordinate session |
| Long Text: | COMMIT was issued in a session that is not the two-phase commit global coordinator. |
| Repair Text: | From Oracle doc: Issue commit at the global coordinator only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2090 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | network error: attempted callback+passthru |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2091 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction rolled back |
| Long Text: | The distributed transaction is assigned to the system rollback segment and is trying to get into the prepared state, but the required number of non-PREPARED slots are not available, so the transaction is rolled back. If the transaction aborted at a remote site, only ORA-02091 will be seen. If the transaction aborted at the host site, then both ORA-02091 and ORA-02092 will be seen. |
| Repair Text: | From Oracle doc: Complete the current transaction and then do the operation required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2092 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | out of transaction table slots for distributed transaction |
| Long Text: | The transaction is assigned to the system rollback segment and is trying to get into the PREPARED state, but the required number of non-PREPARED slots are not available, hence the transaction is rolled back. |
| Repair Text: | From Oracle doc: Add a rollback segment and retry the transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2093 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TRANSACTIONS_PER_ROLLBACK_SEGMENT(%s) more than maximum possible(%s) |
| Long Text: | Value of the parameter specified is greater than allowed on this port. |
| Repair Text: | From Oracle doc: Use default or reduce it to less than the maximum. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2094 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication option not installed |
| Long Text: | The replication option was not installed at this site. Updatable snapshots, deferred RPCs, and other replication features were, therefore, unavailable. |
| Repair Text: | From Oracle doc: Install the replication option. The replication option is not part of the Oracle7 Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2095 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified initialization parameter cannot be modified |
| Long Text: | Specified initialization parameter is not modifiable with this option. |
| Repair Text: | From Oracle doc: Check the Oracle8i Administrator's Guide for information about under what scope the parameter may be modified. For more information about modifying an initialization parameter, see the Oracle8i Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2096 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified initialization parameter is not modifiable with this option |
| Long Text: | Though the initialization parameter is modifiable, it cannot be modified using the specified command. |
| Repair Text: | From Oracle doc: Check the Oracle8i Administrator's Guide for information about under what scope the parameter may be modified |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2097 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter cannot be modified because specified value is invalid |
| Long Text: | Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter. |
| Repair Text: | From Oracle doc: Check the Oracle8i Administrator's Guide for range of acceptable values for this parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2098 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error parsing index-table reference (:I) |
| Long Text: | An incorrect index-table (:I) syntax was encountered. |
| Repair Text: | From Oracle doc: This syntax is for Oracle internal use only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: out of memory (i.e., could not allocate) |
| Long Text: | SQLLIB was unable to allocate enough memory to execute the program. |
| Repair Text: | From Oracle doc: Allocate more memory to the user session and then rerun the program. If the error persists, call Oracle Customer Support for assistance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent cursor cache (uce/cuc mismatch) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent cursor cache (no cuc entry for this uce) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent cursor cache (out-of-range cuc ref) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2104 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent host cache (no cuc available) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent cursor cache (no cuc entry in cache) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent cursor cache (OraCursor nr is bad) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: this pgm too old for run-time library: please re-PCC it |
| Long Text: | The program was precompiled by an older version of the Oracle Precompilers, which is incompatible with this release of SQLLIB. |
| Repair Text: | From Oracle doc: Precompile the program with a newer version of the Oracle Precompilers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: invalid descriptor passed to run-time library |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent host cache (out-of-range sit ref) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: inconsistent host cache (invalid sqi type) |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: heap consistency error |
| Long Text: | This internal error typically indicates a memory-related error. |
| Repair Text: | From Oracle doc: Check the program for memory-related errors, such as invalid pointers or array-bounds violations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCC: SELECT..INTO returns too many rows |
| Long Text: | A SELECT...INTO statement returned more rows than can be stored in the host variable provided. |
| Repair Text: | From Oracle doc: There are three possible solutions: Use the precompiler option SELECT_ERROR=NO. Declare a host variable with a larger array dimension. Declare a cursor or cursor variable for the select statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2140 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid tablespace name |
| Long Text: | An identifier does not follow ALTER TABLESPACE. |
| Repair Text: | From Oracle doc: Specify a tablespace name following ALTER TABLESPACE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2141 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid OFFLINE option |
| Long Text: | An option other than NORMAL or IMMEDIATE follows OFFLINE. |
| Repair Text: | From Oracle doc: The user must either specify no option following OFFLINE or one of the options NORMAL or IMMEDIATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2142 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid ALTER TABLESPACE option |
| Long Text: | A valid option is not present. |
| Repair Text: | From Oracle doc: Use one of the valid options: add, rename, default, online, offline, read only, read write, begin, and end. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2143 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid STORAGE option |
| Long Text: | An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause. |
| Repair Text: | From Oracle doc: Specify only valid options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2144 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no option specified for ALTER CLUSTER |
| Long Text: | No ALTER CLUSTER options are specified. |
| Repair Text: | From Oracle doc: Specify one or more of the following options: PCTFREE, PCTUSED, SIZE, STORAGE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2145 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing STORAGE option |
| Long Text: | No STORAGE options were specified following STORAGE (. |
| Repair Text: | From Oracle doc: Specify one or more STORAGE option between the parentheses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2146 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SHARED specified multiple times |
| Long Text: | The SHARED option was specified in a CREATE DATABASE statement multiple times. |
| Repair Text: | From Oracle doc: Only specify the SHARED option once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2147 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | conflicting SHARED/EXCLUSIVE options |
| Long Text: | Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement. |
| Repair Text: | From Oracle doc: Specify SHARED or EXCLUSIVE, but not both. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2148 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EXCLUSIVE specified multiple times |
| Long Text: | The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times. |
| Repair Text: | From Oracle doc: Only specify the EXCLUSIVE option once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2149 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Specified partition does not exist |
| Long Text: | Partition not found for the object. |
| Repair Text: | From Oracle doc: Retry with correct partition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid VALUES password %s |
| Long Text: | An encoded password string does not follow the VALUES clause. |
| Repair Text: | From Oracle doc: Place a proper encoded password string after the VALUES clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid DEFAULT tablespace identifier |
| Long Text: | An identifier does not follow DEFAULT TABLESPACE. |
| Repair Text: | From Oracle doc: Place a tablespace name after DEFAULT TABLESPACE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2156 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid TEMPORARY tablespace identifier |
| Long Text: | An identifier does not follow TEMPORARY TABLESPACE. |
| Repair Text: | From Oracle doc: Place a tablespace name after TEMPORARY TABLESPACE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2157 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no options specified for ALTER USER |
| Long Text: | No options were specified. |
| Repair Text: | From Oracle doc: Specify at least one ALTER USER option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2158 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CREATE INDEX option |
| Long Text: | An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified. |
| Repair Text: | From Oracle doc: Choose one of the valid CREATE INDEX options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2159 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | installed DLM does not support releasable locking mode |
| Long Text: | The parameter file specified GC_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available. |
| Repair Text: | From Oracle doc: Specify configuration parameters that do not require the additional function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index-organized table can not contain columns of type LONG |
| Long Text: | A column of type LONG defined for index-organized table. |
| Repair Text: | From Oracle doc: Do not use columns of type LONG in index-organized tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for MAXLOGFILES |
| Long Text: | A number does not follow MAXLOGFILES. |
| Repair Text: | From Oracle doc: Specify a number after MAXLOGFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for MAXDATAFILES |
| Long Text: | A number does not follow MAXDATAFILES. |
| Repair Text: | From Oracle doc: Specify a number after MAXDATAFILES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for FREELIST GROUPS |
| Long Text: | A number does not follow FREELIST GROUPS. |
| Repair Text: | From Oracle doc: Specify a number after FREELIST GROUPS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2164 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DATAFILE clause specified more than once |
| Long Text: | The CREATE DATABASE command contains more than one DATAFILE clause. |
| Repair Text: | From Oracle doc: Specify at most one DATAFILE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2165 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for CREATE DATABASE |
| Long Text: | An invalid CREATE DATABASE option is present. |
| Repair Text: | From Oracle doc: Specify only valid CREATE DATABASE options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2166 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ARCHIVELOG and NOARCHIVELOG specified |
| Long Text: | Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement. |
| Repair Text: | From Oracle doc: Specify at most one of these two options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2167 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOGFILE clause specified more than once |
| Long Text: | The CREATE DATABASE command contains more than one LOGFILE clause. |
| Repair Text: | From Oracle doc: Specify at most one LOGFILE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2168 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for FREELISTS |
| Long Text: | A number does not follow FREELISTS. |
| Repair Text: | From Oracle doc: Specify a number after FREELISTS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2169 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | FREELISTS storage option not allowed |
| Long Text: | An attempt was made to specify the FREELISTS storage option. This option may only be specified during create table or create index. |
| Repair Text: | From Oracle doc: Remove these options and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2170 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | FREELIST GROUPS storage option not allowed |
| Long Text: | An attempt was made to specify the FREELIST GROUPS storage option. This option may be specified only when using the CREATE TABLE command and when the ALLOW_FREELIST_GROUPS parameter is specified in the initialization parameter file. |
| Repair Text: | From Oracle doc: Retry the statement without the FREELIST GROUPS storage option or set the ALLOW_FREELIST_GROUPS parameter in the initialization parameter file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2171 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for MAXLOGHISTORY |
| Long Text: | A number does not follow MAXLOGHISTORY. |
| Repair Text: | From Oracle doc: Specify a number after MAXLOGHISTORY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2172 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The PUBLIC keyword is not appropriate for a disable thread |
| Long Text: | The PUBLIC keyword was specified for a disable. |
| Repair Text: | From Oracle doc: Remove the keyword and resubmit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2173 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for DROP TABLESPACE |
| Long Text: | Either a token other than INCLUDING was found following the tablespace name or some text was found following INCLUDING CONTENTS. |
| Repair Text: | From Oracle doc: Place nothing or only INCLUDING CONTENTS after the tablespace name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2174 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Missing required thread number |
| Long Text: | A thread number must be specified after THREAD keyword. |
| Repair Text: | From Oracle doc: Use correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2175 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid rollback segment name |
| Long Text: | In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT. |
| Repair Text: | From Oracle doc: Place the segment name following ROLLBACK SEGMENT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2176 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for CREATE ROLLBACK SEGMENT |
| Long Text: | An invalid option was specified in a CREATE ROLLBACK SEGMENT statement. |
| Repair Text: | From Oracle doc: Specify one of the valid options: TABLESPACE and STORAGE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2177 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Missing required group number |
| Long Text: | A group number must be specified after GROUP keyword. |
| Repair Text: | From Oracle doc: Check the syntax of the command, specify a group number after GROUP, and retry it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2178 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | correct syntax is: SET TRANSACTION READ { ONLY | WRITE } |
| Long Text: | There is a syntax error in the user's statement. |
| Repair Text: | From Oracle doc: Correct the syntax as indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2179 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED } |
| Long Text: | There is a syntax error in the user's statement. |
| Repair Text: | From Oracle doc: Correct the syntax as indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2180 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for CREATE TABLESPACE |
| Long Text: | An invalid option appears. |
| Repair Text: | From Oracle doc: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2181 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option to ROLLBACK WORK |
| Long Text: | A token other than TO follows ROLLBACK [WORK]. |
| Repair Text: | From Oracle doc: Place nothing or TO SAVEPOINT name after ROLLBACK [WORK]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2182 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | savepoint name expected |
| Long Text: | An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT]. |
| Repair Text: | From Oracle doc: Place a savepoint name following TO [SAVEPOINT]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2183 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED } |
| Long Text: | There is a syntax error in the user's statement. |
| Repair Text: | From Oracle doc: Correct the syntax as indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2184 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resource quotas are not allowed in REVOKE |
| Long Text: | In a revoke statement, a resource quota was specified. |
| Repair Text: | From Oracle doc: Specify resource privilege without the quota. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2185 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a token other than WORK follows COMMIT |
| Long Text: | A token other than WORK follows COMMIT. |
| Repair Text: | From Oracle doc: Place either nothing or WORK after COMMIT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2186 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace resource privilege may not appear with other privileges |
| Long Text: | An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked. |
| Repair Text: | From Oracle doc: Use a separate grant or revoke statement for the resource quota privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2187 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid quota specification |
| Long Text: | In a grant or revoke statement, an attempt was made to grant a tablespace quota above the upper limit. |
| Repair Text: | From Oracle doc: Grant a smaller tablespace quota. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2189 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ON tablespace required |
| Long Text: | In a grant or revoke statement, the user specified a tablespace quota but did not follow it with the ON tablespace clause. |
| Repair Text: | From Oracle doc: Specify the tablespace on which the quota is to be applied with the ON tablespace clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2190 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword TABLES expected |
| Long Text: | The keyword TABLES is expected following DROP CLUSTER name INCLUDING. |
| Repair Text: | From Oracle doc: Place TABLES after INCLUDING. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2191 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT rbs |
| Long Text: | There is a syntax error in the user's statement. |
| Repair Text: | From Oracle doc: Correct the syntax as indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2192 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCTINCREASE not allowed for rollback segment storage clauses |
| Long Text: | The storage parameter PCTINCREASE was specified in a CREATE or ALTER ROLLBACK SEGMENT command. |
| Repair Text: | From Oracle doc: Retry the command without the PCTINCREASE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2194 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | event specification syntax error %s (minor error %s) near '%s' |
| Long Text: | There is a syntax error in an event specification. |
| Repair Text: | From Oracle doc: Check syntax and spelling and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2195 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Attempt to create %s object in a %s tablespace |
| Long Text: | The object type is inconsistent with a tablespace contents. |
| Repair Text: | From Oracle doc: Create an object in a different tablespace, or change the user defaults. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2196 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PERMANENT/TEMPORARY option already specified |
| Long Text: | In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once. |
| Repair Text: | From Oracle doc: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE. For more information about the parameters of CREATE TABLESPACE, see Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2197 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file list already specified |
| Long Text: | In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified. |
| Repair Text: | From Oracle doc: Merge the DATAFILE/TEMPFILE clauses into a single clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2198 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ONLINE/OFFLINE option already specified |
| Long Text: | In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once. |
| Repair Text: | From Oracle doc: Specify at most one of ONLINE or OFFLINE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2199 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing DATAFILE/TEMPFILE clause |
| Long Text: | A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause. |
| Repair Text: | From Oracle doc: Specify a DATAFILE/TEMPFILE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | WITH GRANT OPTION not allowed for PUBLIC |
| Long Text: | An attempt was made to GRANT to PUBLIC WITH GRANT OPTION. |
| Repair Text: | From Oracle doc: Remove the WITH GRANT OPTION clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence not allowed here |
| Long Text: | An attempt was made to reference a sequence in a from-list. |
| Repair Text: | From Oracle doc: A sequence can only be referenced in a select-list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no more tables permitted in this cluster |
| Long Text: | An attempt was made to create a table in a cluster which already contains 32 tables. |
| Repair Text: | From Oracle doc: Up to 32 tables may be stored per cluster. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | INITIAL storage options not allowed |
| Long Text: | An attempt was made to alter the INITIAL storage option of a table, cluster, index, or rollback segment. These options may only be specified when the object is created. |
| Repair Text: | From Oracle doc: Remove these options and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER, INDEX, REFERENCE and EXECUTE not allowed for views |
| Long Text: | An attempt was made to grant or revoke an invalid privilege on a view. |
| Repair Text: | From Oracle doc: Do not attempt to grant or revoke any of ALTER, INDEX, or REFERENCES privileges on views. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only SELECT and ALTER privileges are valid for sequences |
| Long Text: | An attempt was made to grant or revoke an invalid privilege on a sequence. |
| Repair Text: | From Oracle doc: Do not attempt to grant or revoke DELETE, INDEX, INSERT, UPDATE, REFERENCES or EXECUTE privilege on sequences. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate INITRANS option specification |
| Long Text: | INITRANS is specified more than once. |
| Repair Text: | From Oracle doc: Specify INITRANS at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid INITRANS option value |
| Long Text: | The INITRANS value is not an integer between 1 and 255 and less than or equal to the MAXTRANS value. |
| Repair Text: | From Oracle doc: Choose a valid INITRANS value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate MAXTRANS option specification |
| Long Text: | MAXTRANS is specified more than once. |
| Repair Text: | From Oracle doc: Specify MAXTRANS at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid MAXTRANS option value |
| Long Text: | The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value. |
| Repair Text: | From Oracle doc: Choose a valid MAXTRANS value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no options specified for ALTER TABLE |
| Long Text: | No ALTER TABLE option was specified. |
| Repair Text: | From Oracle doc: Specify at least one alter table option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for PCTFREE or PCTUSED |
| Long Text: | The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100. |
| Repair Text: | From Oracle doc: Choose an appropriate value for the option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate PCTFREE option specification |
| Long Text: | PCTFREE option specified more than once. |
| Repair Text: | From Oracle doc: Specify PCTFREE at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate PCTUSED option specification |
| Long Text: | PCTUSED option specified more than once. |
| Repair Text: | From Oracle doc: Specify PCTUSED at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate BACKUP option specification |
| Long Text: | The BACKUP option to ALTER TABLE is specified more than once. |
| Repair Text: | From Oracle doc: Specify the option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate tablespace name clause |
| Long Text: | There is more than one TABLESPACE clause in the CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT statement. |
| Repair Text: | From Oracle doc: Specify at most one TABLESPACE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace name expected |
| Long Text: | A tablespace name is not present where required by the syntax for one of the following statements: CREATE/DROP TABLESPACE, CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT. |
| Repair Text: | From Oracle doc: Specify a tablespace name where required by the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate storage option specification |
| Long Text: | A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once. |
| Repair Text: | From Oracle doc: Specify all storage options at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid INITIAL storage option value |
| Long Text: | The specified value must be an integer. |
| Repair Text: | From Oracle doc: Choose an appropriate integer value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid NEXT storage option value |
| Long Text: | The specified value must be an integer. |
| Repair Text: | From Oracle doc: Choose an appropriate integer value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2220 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid MINEXTENTS storage option value |
| Long Text: | The specified value must be a positive integer less than or equal to MAXEXTENTS. |
| Repair Text: | From Oracle doc: Specify an appropriate value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2221 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid MAXEXTENTS storage option value |
| Long Text: | The specified value must be a positive integer greater than or equal to MINEXTENTS. |
| Repair Text: | From Oracle doc: Specify an appropriate value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2222 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid PCTINCREASE storage option value |
| Long Text: | The specified value must be a positive integer. |
| Repair Text: | From Oracle doc: Specify an appropriate value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2223 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid OPTIMAL storage option value |
| Long Text: | The specified value must be an integer. |
| Repair Text: | From Oracle doc: Choose an appropriate integer value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2224 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EXECUTE privilege not allowed for tables |
| Long Text: | An attempt was made to grant or revoke an invalid privilege on a table. |
| Repair Text: | From Oracle doc: Do not attempt to grant or revoke EXECUTE privilege on tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2225 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only EXECUTE privilege is valid for procedures |
| Long Text: | An attempt was made to grant or revoke an invalid privilege on a procedure, function or package. |
| Repair Text: | From Oracle doc: Do not attempt to grant or revoke any privilege besides EXECUTE on procedures, functions or packages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2226 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid MAXEXTENTS value (max allowed: %s) |
| Long Text: | The MAXEXTENTS specified is too large for the database block size. This applies only to SYSTEM rollback segment. |
| Repair Text: | From Oracle doc: Specify a smaller value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2227 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid cluster name |
| Long Text: | A cluster name was not properly formed. |
| Repair Text: | From Oracle doc: Check the rules for forming object names and enter an appropriate cluster name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2228 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate SIZE specification |
| Long Text: | The SIZE option is specified more than once. |
| Repair Text: | From Oracle doc: Specify the SIZE option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2229 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SIZE option value |
| Long Text: | The specified value must be an integer number of bytes. |
| Repair Text: | From Oracle doc: Specify an appropriate value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER CLUSTER option |
| Long Text: | An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE is specified in an ALTER CLUSTER statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid option to ALTER DATABASE |
| Long Text: | An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid MOUNT mode |
| Long Text: | A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement. |
| Repair Text: | From Oracle doc: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CLOSE mode |
| Long Text: | A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement. |
| Repair Text: | From Oracle doc: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | changes to this table are already logged |
| Long Text: | The log table to be added is a duplicate of another. |
| Repair Text: | From Oracle doc: Do not add this change log to the system; check that the replication product's system tables are consistent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this table logs changes to another table already |
| Long Text: | The table to be altered is already a change log for another table. |
| Repair Text: | From Oracle doc: Do not log changes to the specified base table to this table; check that the replication product's system tables are consistent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2236 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid file name |
| Long Text: | A character string literal was not used in the file name list of a LOGFILE, DATAFILE, or RENAME clause. |
| Repair Text: | From Oracle doc: Use correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2237 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid file size |
| Long Text: | A non-integer value was specified in the SIZE or RESIZE clause. |
| Repair Text: | From Oracle doc: Use correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2238 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | filename lists have different numbers of files |
| Long Text: | In a RENAME clause in ALTER DATABASE or TABLESPACE, the number of existing file names does not equal the number of new file names. |
| Repair Text: | From Oracle doc: Make sure there is a new file name to correspond to each existing file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2239 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | there are objects which reference this sequence |
| Long Text: | The sequence to be dropped is still referenced by other objects. |
| Repair Text: | From Oracle doc: Make sure the sequence name is correct or drop the constraint or object that references the sequence. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2240 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for OBJNO or TABNO |
| Long Text: | A number does not follow either OBJNO or TABNO. |
| Repair Text: | From Oracle doc: Specify a number after OBJNO or TABNO. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2241 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must of form EXTENTS (FILE n BLOCK n SIZE n, ...) |
| Long Text: | There was an error in the extent storage clause. |
| Repair Text: | From Oracle doc: Respecify the storage clause using the correct syntax and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2242 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no options specified for ALTER INDEX |
| Long Text: | No options specified. |
| Repair Text: | From Oracle doc: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2243 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER INDEX or ALTER SNAPSHOT option |
| Long Text: | An option other than INITRANS, MAXTRANS, or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2244 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER ROLLBACK SEGMENT option |
| Long Text: | The STORAGE option is expected but not found. |
| Repair Text: | From Oracle doc: Specify the STORAGE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2245 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ROLLBACK SEGMENT name |
| Long Text: | An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT. |
| Repair Text: | From Oracle doc: Place a rollback segment name following SEGMENT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2246 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing EVENTS text |
| Long Text: | A character string literal was expected, but not found, following ALTER SESSION SET EVENTS. |
| Repair Text: | From Oracle doc: Place the string literal containing the events text after EVENTS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2247 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no option specified for ALTER SESSION |
| Long Text: | The option SET EVENTS was expected, but not found, following ALTER SESSION. |
| Repair Text: | From Oracle doc: Place the SET EVENTS option after ALTER SESSION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2248 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for ALTER SESSION |
| Long Text: | An option other than SET EVENTS was found following the ALTER SESSION command. |
| Repair Text: | From Oracle doc: Specify the SET EVENTS option after the ALTER SESSION command and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2249 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid value for MAXLOGMEMBERS |
| Long Text: | A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the port-specific maximum number of log file members. |
| Repair Text: | From Oracle doc: Specify a valid number after MAXLOGMEMBERS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid constraint name |
| Long Text: | The constraint name is missing or invalid. |
| Repair Text: | From Oracle doc: Specify a valid identifier name for the constraint name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subquery not allowed here |
| Long Text: | Subquery is not allowed here in the statement. |
| Repair Text: | From Oracle doc: Remove the subquery from the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2252 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | check constraint condition not properly ended |
| Long Text: | The specified search condition for the check constraint is not properly ended. |
| Repair Text: | From Oracle doc: End the condition properly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2253 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | constraint specification not allowed here |
| Long Text: | Constraint specification is not allowed here in the statement. |
| Repair Text: | From Oracle doc: Remove the constraint specification from the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2254 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DEFAULT expression not allowed here |
| Long Text: | Default value expression is not allowed for the column here in the statement. |
| Repair Text: | From Oracle doc: Remove the default value expression from the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2255 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NOT NULL not allowed after DEFAULT NULL |
| Long Text: | A NOT NULL specification conflicts with the NULL default value. |
| Repair Text: | From Oracle doc: Remove either the NOT NULL or the DEFAULT NULL specification and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2256 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of referencing columns must match referenced columns |
| Long Text: | The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list. |
| Repair Text: | From Oracle doc: Make sure that the referencing columns match the referenced columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2257 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of columns exceeded |
| Long Text: | The number of columns in the key list exceeds the maximum number. |
| Repair Text: | From Oracle doc: Reduce the number columns in the list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2258 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate or conflicting NULL and/or NOT NULL specifications |
| Long Text: | A duplicate or conflicting NULL and/or NOT NULL was specified. |
| Repair Text: | From Oracle doc: Remove one of the conflicting specifications and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2259 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate UNIQUE/PRIMARY KEY specifications |
| Long Text: | A duplicate unique or primary key was specified. |
| Repair Text: | From Oracle doc: Remove the duplicate specification and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table can have only one primary key |
| Long Text: | Two or more primary keys were specified for the same table. |
| Repair Text: | From Oracle doc: Remove the extra primary keys and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | such unique or primary key already exists in the table |
| Long Text: | A unique or primary key was specified that already exists for the table. |
| Repair Text: | From Oracle doc: Remove the extra key and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORA-nnnnn occurs while type-checking column default value expression |
| Long Text: | New column datatype causes type-checking error for existing column default value expression. |
| Repair Text: | From Oracle doc: Remove the default value expression or do not alter the column datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | need to specify the datatype for this column |
| Long Text: | The required datatype for the column is missing. |
| Repair Text: | From Oracle doc: Specify the required datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2264 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name already used by an existing constraint |
| Long Text: | The specified constraint name has to be unique. |
| Repair Text: | From Oracle doc: Specify a unique constraint name for the constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot derive the datatype of the referencing column |
| Long Text: | The datatype of the referenced column is not defined as yet. |
| Repair Text: | From Oracle doc: Make sure that the datatype of the referenced column is defined before referencing it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unique/primary keys in table referenced by enabled foreign keys |
| Long Text: | An attempt was made to drop or truncate a table with unique or primary keys referenced by foreign keys enabled in another table. |
| Repair Text: | From Oracle doc: Before dropping or truncating the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: select constraint_name, table_name, status |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2267 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column type incompatible with referenced column type |
| Long Text: | The datatype of the referencing column is incompatible with the datatype of the referenced column. |
| Repair Text: | From Oracle doc: Select a compatible datatype for the referencing column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2268 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referenced table does not have a primary key |
| Long Text: | The referenced table does not have a primary key. |
| Repair Text: | From Oracle doc: Specify explicitly the referenced table unique key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2269 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | key column cannot be of LONG datatype |
| Long Text: | An attempt was made to define a key column of datatype LONG. This is not allowed. |
| Repair Text: | From Oracle doc: Change the datatype of the column or remove the LONG column from the key, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no matching unique or primary key for this column-list |
| Long Text: | An attempt was made to reference a unique or primary key in a table with a CREATE or ALTER TABLE statement when no such key exists in the referenced table. |
| Repair Text: | From Oracle doc: Add the unique or primary key to the table or find the correct names of the columns with the primary or unique key, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table does not have such constraint |
| Long Text: | An attempt was made to reference a table using a constraint that does not exist. |
| Repair Text: | From Oracle doc: Check the spelling of the constraint name or add the constraint to the table, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2272 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | constrained column cannot be of LONG datatype |
| Long Text: | A constrained column cannot be defined as datatype LONG. This is not allowed. |
| Repair Text: | From Oracle doc: Change the datatype of the column or remove the constraint on the column, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2273 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this unique/primary key is referenced by some foreign keys |
| Long Text: | A unique or primary key referenced by foreign keys cannot be dropped. |
| Repair Text: | From Oracle doc: Remove all references to the key before dropping it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2274 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate referential constraint specifications |
| Long Text: | A referential constraint was specified more than once. This is not allowed. |
| Repair Text: | From Oracle doc: Remove the duplicate specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2275 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | such a referential constraint already exists in the table |
| Long Text: | An attempt was made to specify a referential constraint that already exists. This would result in duplicate specifications and so is not allowed. |
| Repair Text: | From Oracle doc: Be sure to specify a constraint only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | default value type incompatible with column type |
| Long Text: | The type of the evaluated default expression is incompatible with the datatype of the column. |
| Repair Text: | From Oracle doc: Change the type of the column, or modify the default expression. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid sequence name |
| Long Text: | The specified sequence name is not a valid identifier name. |
| Repair Text: | From Oracle doc: Specify a valid identifier name for the sequence name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate or conflicting MAXVALUE/NOMAXVALUE specifications |
| Long Text: | Duplicate or conflicting MAXVALUE and/or NOMAXVALUE specifications. |
| Repair Text: | From Oracle doc: Remove one of the conflicting specifications and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2279 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate or conflicting MINVALUE/NOMINVALUE specifications |
| Long Text: | Duplicate or conflicting MINVALUE and/or NOMINVALUE clauses were specified. |
| Repair Text: | From Oracle doc: Remove one of the conflicting specifications and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2280 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate or conflicting CYCLE/NOCYCLE specifications |
| Long Text: | Duplicate or conflicting CYCLE and/or NOCYCLE clauses were specified. |
| Repair Text: | From Oracle doc: Remove one of the conflicting specifications and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate or conflicting CACHE/NOCACHE specifications |
| Long Text: | Duplicate or conflicting CACHE and/or NOCACHE clauses were specified. |
| Repair Text: | From Oracle doc: Remove one of the conflicting specifications and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2282 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate or conflicting ORDER/NOORDER specifications |
| Long Text: | Duplicate or conflicting ORDER and/or NOORDER clauses were specified. |
| Repair Text: | From Oracle doc: Remove one of the conflicting specifications and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2283 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot alter starting sequence number |
| Long Text: | An attempt was made to alter a starting sequence number. This is not allowed. |
| Repair Text: | From Oracle doc: Do not try to alter a starting sequence number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2284 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate INCREMENT BY specifications |
| Long Text: | A duplicate INCREMENT BY clause was specified. |
| Repair Text: | From Oracle doc: Remove the duplicate specification and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2285 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate START WITH specifications |
| Long Text: | A duplicate START WITH clause was specified. |
| Repair Text: | From Oracle doc: Remove the duplicate specification and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2286 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | no options specified for ALTER SEQUENCE |
| Long Text: | No ALTER SEQUENCE option was specified. |
| Repair Text: | From Oracle doc: Check the syntax. Then specify at least one ALTER SEQUENCE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2287 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | sequence number not allowed here |
| Long Text: | The specified sequence number reference, CURRVAL or NEXTVAL, is inappropriate at this point in the statement. |
| Repair Text: | From Oracle doc: Check the syntax. Then remove or relocate the sequence number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2288 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid OPEN mode |
| Long Text: | A mode other than RESETLOGS was specified in an ALTER DATABASE OPEN statement. RESETLOGS is the only valid OPEN mode. |
| Repair Text: | From Oracle doc: Remove the invalid mode from the statement or replace it with the keyword RESETLOGS, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2289 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence does not exist |
| Long Text: | The specified sequence does not exist, or the user does not have the required privilege to perform this operation. |
| Repair Text: | From Oracle doc: Make sure the sequence name is correct, and that you have the right to perform the desired operation on this sequence. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | check constraint (%s.%s) violated |
| Long Text: | The value or values attempted to be entered in a field or fields violate a defined check constraint. |
| Repair Text: | From Oracle doc: Enter values that satisfy the constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2291 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | integrity constraint (%s.%s) violated - parent key not found |
| Long Text: | A foreign key value has no matching primary key value. |
| Repair Text: | From Oracle doc: Delete the foreign key or add a matching primary key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2292 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | integrity constraint (%s.%s) violated - child record found |
| Long Text: | An attempt was made to delete a row that is referenced by a foreign key. |
| Repair Text: | From Oracle doc: It is necessary to DELETE or UPDATE the foreign key before changing this row. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2293 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot validate (%s.%s) - check constraint violated |
| Long Text: | An attempt was made via an ALTERTABLE statement to add a check constraint to a populated table that had no complying values. |
| Repair Text: | From Oracle doc: Retry the ALTER TABLE statement, specifying a check constraint on a table containing complying values. For more information about ALTER TABLE, see Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2294 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot enable (%s.%s) - constraint changed during validation |
| Long Text: | While one DDL statement was attempting to enable this constraint, another DDL changed this same constraint. |
| Repair Text: | From Oracle doc: Try again, with only one DDL changing the constraint this time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2295 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | found more than one enable/disable clause for constraint |
| Long Text: | An attempt was made via a CREATE or ALTER TABLE statement to specify more than one ENABLE and/or DISABLE clause for a given constraint. |
| Repair Text: | From Oracle doc: Only one ENABLE or DISABLE clause may be specified for a given constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2296 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot enable (%s.%s) - null values found |
| Long Text: | An ALTER TABLE command with an ENABLE CONSTRAINT clause failed because the table contains values that do not satisfy the constraint. |
| Repair Text: | From Oracle doc: Make sure that all values in the table satisfy the constraint before issuing an ALTER TABLE command with an ENABLE CONSTRAINT clause. For more information about ALTER TABLE and ENABLE CONSTRAINT, see Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2297 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot disable constraint (%s.%s) - dependencies exist |
| Long Text: | An alter table disable constraint failed because the table has foreign keys that are dependent on the constraint. |
| Repair Text: | From Oracle doc: Either disable the foreign key constraints or use a DISABLE CASCADE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2298 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot validate (%s.%s) - parent keys not found |
| Long Text: | An ALTER TABLE ENABLE CONSTRAINT command failed because the table has orphaned child records. |
| Repair Text: | From Oracle doc: Make sure that the table has no orphaned child records before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2299 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot validate (%s.%s) - duplicate keys found |
| Long Text: | An ALTER TABLE ENABLE CONSTRAINT command failed because the table has duplicate key values. |
| Repair Text: | From Oracle doc: Make sure that the table has no duplicate key values before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for OIDGENERATORS |
| Long Text: | A number was not specified for the value of OIDGENERATORS. |
| Repair Text: | From Oracle doc: Specify a number for OIDGENERATORS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of OIDGENERATORS is 255 |
| Long Text: | A number greater than 255 was specified for the value of OIDGENERATORS. |
| Repair Text: | From Oracle doc: Make sure the number specified for OIDGENERATORS does not exceed 255. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or missing type name |
| Long Text: | An invalid or missing type name was entered in a statement. |
| Repair Text: | From Oracle doc: Enter a valid type name in the statement and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop or replace a type with type or table dependents |
| Long Text: | An attempt was made to drop or replace a type that has dependents. |
| Repair Text: | From Oracle doc: Drop all type(s) and table(s) depending on the type, then retry the operation, or use the FORCE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid object identifier literal |
| Long Text: | An attempt was made to enter an object identifier literal for CREATE TYPE that is either: Not a string of 32 hexadecimal characters An object identifier that already identifies an existing object An object identifier different from the original object identifier already assigned to the type |
| Repair Text: | From Oracle doc: Do not specify the object identifier clause or specify a 32 hexadecimal-character object identifier literal that is unique or identical to the originally assigned object identifier. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only EXECUTE privilege is valid for types |
| Long Text: | An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE) on a type. |
| Repair Text: | From Oracle doc: GRANT or REVOKE only the EXECUTE privilege on types. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a type that already has valid dependent(s) |
| Long Text: | An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist). |
| Repair Text: | From Oracle doc: Drop the dependents first before creating the type, or do not create the type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2307 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot alter with REPLACE option a type that is not valid |
| Long Text: | An attempt was made to ALTER with REPLACE option a type that is not valid. |
| Repair Text: | From Oracle doc: Use the CREATE OR REPLACE TYPE command to modify the type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2308 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option %s for object type column |
| Long Text: | An attempt was made to specify an invalid option, such as PACKED or UNPACKED, for the object type column. |
| Repair Text: | From Oracle doc: Remove the invalid option from column specification and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | atomic NULL violation |
| Long Text: | An attempt was made to access the attributes of a NULL object instance. |
| Repair Text: | From Oracle doc: Ensure that the object instance is non-NULL before accessing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded maximum number of allowable columns in table |
| Long Text: | The attributes in the object type column exceeded the maximum number of columns allowed in a table. |
| Repair Text: | From Oracle doc: Specify fewer attributes for the object type and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot alter with COMPILE option a valid type with type or table dependents |
| Long Text: | An attempt was made to ALTER with COMPILE option a type that is valid and has type or table dependents. |
| Repair Text: | From Oracle doc: No need to perform this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2312 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create extent table for VALUE ADT |
| Long Text: | An attempt was made to create extent table for VALUE Object Type. |
| Repair Text: | From Oracle doc: Specify object type when creating extent table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object type contains non-queryable type %s attribute |
| Long Text: | The specified object type contains a nested attribute whose type is non-queryable. |
| Repair Text: | From Oracle doc: Use an object type with queryable attribute types. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create index on object type column or attribute |
| Long Text: | An attempt was made to create an index on an object type column. |
| Repair Text: | From Oracle doc: index can only be created on simple, scalar columns or attributes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect number of arguments for default constructor |
| Long Text: | The number of arguments specified for the default constructor does not match the number of attributes of the object type. |
| Repair Text: | From Oracle doc: Specify the correct number of arguments for the default constructor and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect number of attributes in object type column |
| Long Text: | The number of attributes in object type operand does not match number of attributes in object type column to be updated. |
| Repair Text: | From Oracle doc: Make sure both object type attributes match. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid operation for object type operands |
| Long Text: | An invalid operation on object type operands was specified. |
| Repair Text: | From Oracle doc: Make sure the correct operation is requested to be performed on object type operands. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid REF function on non-object table |
| Long Text: | An invalid REF operator was specified for a non-object table. REF operator can only be specified on an object table. |
| Repair Text: | From Oracle doc: Do not specify a REF operator on a non-object table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid column argument to REF operator |
| Long Text: | An invalid REF column argument was specified. The argument to a REF operator can only be the object type column of the object table. |
| Repair Text: | From Oracle doc: Specify a valid REF column argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2320 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure in creating storage table for nested table column %s |
| Long Text: | An error occurred while creating the storage table for the specified nested table column. |
| Repair Text: | From Oracle doc: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object type's default constructor expected |
| Long Text: | The expected constructor was not found. |
| Repair Text: | From Oracle doc: Specify an ADT default constructor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure in accessing storage table of the nested table column |
| Long Text: | An error occurred while performing DML on the storage table of the nested table column. |
| Repair Text: | From Oracle doc: If the situation described in the following messages can be corrected, do so; otherwise contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2323 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fail in %s inner table for column %s |
| Long Text: | An error occurred while performing DML on the nested table column. |
| Repair Text: | From Oracle doc: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2324 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | more than one column in the SELECT list of THE subquery |
| Long Text: | More than one column was selected in the THE subquery. |
| Repair Text: | From Oracle doc: Specify only one column in the SELECT list of the THE subquery and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2325 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | zero rows returned by THE subquery |
| Long Text: | THE subquery evaluation returns no rows whereas it is supposed to return a single row. |
| Repair Text: | From Oracle doc: Change the subquery within THE operator to return exactly one row. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2326 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing THE keyword |
| Long Text: | Subquery used to return an inner nested table is enclosed by THE operator. |
| Repair Text: | From Oracle doc: Put THE operator around the subquery; for example, THE(subquery). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2327 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create index on expression with datatype %s |
| Long Text: | An attempt was made to create an index on a non-indexable expression. |
| Repair Text: | From Oracle doc: Change the column datatype or do not create the index on an expression whose datatype is one of VARRAY, nested table, object, LOB, or REF. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2328 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REF column cannot be specified on VALUE ADT |
| Long Text: | An attempt was made to create a REF column of VALUE ADT. |
| Repair Text: | From Oracle doc: Remove the REF specifier from the column specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2329 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column of datatype %s cannot be unique or a primary key |
| Long Text: | An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF. |
| Repair Text: | From Oracle doc: Change the column datatype or remove the constraint. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2330 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datatype specification not allowed |
| Long Text: | An attempt was made to specify the data type in the column constraint specification of an object table. |
| Repair Text: | From Oracle doc: Remove data type specification and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2331 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create constraint on column of datatype %s |
| Long Text: | An attempt was made to create a constraint on a column possessing a non-constrainable datatype: VARRAY, nested table, object, LOB, FILE, or REF. |
| Repair Text: | From Oracle doc: Change the column datatype, or remove the constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2332 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create index on attributes of this column |
| Long Text: | An attempt was made to create an index on an attributes of an object type column. |
| Repair Text: | From Oracle doc: Do not specify the index on the attribute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2333 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create constraints on attributes of this column |
| Long Text: | An attempt was made to create a constraint on an attribute of an object type column. |
| Repair Text: | From Oracle doc: Remove the constraint or change the object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2334 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot infer type for column |
| Long Text: | A datatype was not declared for this column (in the CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column. |
| Repair Text: | From Oracle doc: Declare a datatype for the column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid datatype for cluster column |
| Long Text: | An attempt was made to declare a CLUSTER column of datatype object, REF, nested table, VARRAY, LOB, or FILE. |
| Repair Text: | From Oracle doc: Remove the CLUSTER column or change the datatype of the column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2336 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column attribute cannot be accessed |
| Long Text: | An attempt was made to extract an attribute of an object type column. |
| Repair Text: | From Oracle doc: Change the object type for the column and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2337 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not an object type column |
| Long Text: | An attempt was made to use dotted notation on a non-ADT column; that is, "a.b.c" where "a" is not an object type. |
| Repair Text: | From Oracle doc: Either change the column type to an object type or do not perform this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2338 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid column constraint specification |
| Long Text: | A column constraint was not specified. |
| Repair Text: | From Oracle doc: Remove the column specification or specify a column constraint. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2339 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid column specification |
| Long Text: | An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column. |
| Repair Text: | From Oracle doc: Remove the PACKED or UNPACKED keyword in the column specification and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid column specification |
| Long Text: | An attempt was made to specify an UNPACKED column within a packed table. |
| Repair Text: | From Oracle doc: Remove the UNPACKED keyword in the column specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot refer to non-queryable type %s in SQL |
| Long Text: | Attempt to refer to an object type attribute that is of a non-queryable type in SQL. |
| Repair Text: | From Oracle doc: Change attribute type to a SQL-queryable type, or reference the attribute through a 3GL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replacement type has compilation errors |
| Long Text: | The use of the ALTER...REPLACE statement on a valid type caused a compilation error. |
| Repair Text: | From Oracle doc: Use the ALTER...REPLACE statement to replace the type with a valid type which does not cause compilation errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot revoke execute on a type with table dependents |
| Long Text: | An attempt was made to revoke execute on a type that has dependents. |
| Repair Text: | From Oracle doc: Drop all table(s) depending on the type, then retry the operation, or use the FORCE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a view with column based on CURSOR operator |
| Long Text: | A CURSOR operator was used as one of the SELECT elements in the subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement. |
| Repair Text: | From Oracle doc: Remove the CURSOR operator and replace it with the CAST operator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2347 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot grant privileges on columns of an object table |
| Long Text: | An attempt was made to grant privileges on the columns of an object table. |
| Repair Text: | From Oracle doc: Choose another table. Privileges cannot be granted on columns of an object table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2348 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid attribute type |
| Long Text: | Object type columns cannot have attributes of type LOB or nested table. |
| Repair Text: | From Oracle doc: Remove the invalid attribute from the type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2349 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid user-defined type - type is incomplete |
| Long Text: | An attempt was made to use an incomplete type definition as a column or table datatype. |
| Repair Text: | From Oracle doc: Complete the type definition and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot insert into attributes of a packed typed table |
| Long Text: | A column list was specified in an INSERT statement. |
| Repair Text: | From Oracle doc: Drop the column list specification statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Record %s: Rejected - Error on table %s, column %s |
| Long Text: | The record indicated caused an Oracle error on insert. |
| Repair Text: | From Oracle doc: Determine the Oracle error and correct the record. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Direct path connection must be homogeneous |
| Long Text: | The user-side to kernel-side connection is heterogeneous. |
| Repair Text: | From Oracle doc: Make the connection between identical hardware and operating systems. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Multibyte character error |
| Long Text: | Text specified by POSITION or terminated by newlines is invalid. |
| Repair Text: | From Oracle doc: Edit the control file or the datafile to fix alignment of column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Conversion initialization error occurred on field %s |
| Long Text: | An error occurred during conversion initialization for a field. This is an internal error. |
| Repair Text: | From Oracle doc: Contact customer support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2355 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Conversion error occurred on CONSTANT field %s |
| Long Text: | A CONSTANT field caused an Oracle error; all rows will be rejected. |
| Repair Text: | From Oracle doc: Determine the Oracle error and correct the record. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2356 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The database is out of space. The load cannot continue |
| Long Text: | The load was discontinued due to space exhaustion in the database. |
| Repair Text: | From Oracle doc: Add space for the specified table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2357 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Packed Decimal conversion error |
| Long Text: | The column could not be converted from packed decimal to character. |
| Repair Text: | From Oracle doc: Check the column and make it conform to packed decimal format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2358 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Zoned Decimal conversion error |
| Long Text: | The column could not be converted from packed decimal to character. |
| Repair Text: | From Oracle doc: Check the column and make it conform to packed decimal format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2359 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Field in data file exceeded maximum specified length |
| Long Text: | The field is too long for the specified column. |
| Repair Text: | From Oracle doc: Shorten the field so that its length is less than or equal to the column length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Column not found before end of logical record (use TRAILING NULLCOLS) |
| Long Text: | A column started after the end of the logical record had been reached. |
| Repair Text: | From Oracle doc: Use the TRAILING NULLCOLS option or supply data for the column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Initial enclosing character not found |
| Long Text: | The initial enclosing character of an enclosed field was not found. |
| Repair Text: | From Oracle doc: Supply the character before the start of the field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Logical record ended - second enclosing character not present |
| Long Text: | The second enclosing character of an enclosed field was not found. |
| Repair Text: | From Oracle doc: Supply the character after the end of the field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No terminator found after TERMINATED and ENCLOSED field |
| Long Text: | No terminator was found after a terminated and enclosed field. |
| Repair Text: | From Oracle doc: Supply the character after the end of the field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2364 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Record %s: Discarded - failed all WHEN clauses |
| Long Text: | The record was not loaded because it failed the WHEN clauses of all the tables. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2365 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Index %s was made Index Unusable due to |
| Long Text: | The index was not loaded. The cause of the error is stated after the message. |
| Repair Text: | From Oracle doc: Correct the cause of the error, then reload. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2366 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | The following index(es) on table %s were processed: |
| Long Text: | The indexes listed for the named table were loaded. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2367 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | Index %s was loaded. |
| Long Text: | The index specified in the message was loaded. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2368 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Record %s: Discarded - all columns null. |
| Long Text: | The record was not loaded because all of the columns in the table were null for that record. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Warning: Variable length field was truncated. |
| Long Text: | A variable length field was truncated by the end of the logical record. |
| Repair Text: | From Oracle doc: This is just a warning, but since a variable length field has the length embedded in the data for each row, you may want to check your data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2370 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Record %s - Warning on table %s, column %s |
| Long Text: | The record indicated caused an warning. |
| Repair Text: | From Oracle doc: Determine the warning and correct the record if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2371 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Loader must be at least version %s.%s.%s.%s.%s for direct path |
| Long Text: | The loader being used is incompatible with this version of the kernel. |
| Repair Text: | From Oracle doc: Upgrade your loader to at least the specified version or use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2372 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Relative start position > absolute field end position. |
| Long Text: | A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y. |
| Repair Text: | From Oracle doc: Check that you are not missing a delimiter and that the values of n and y are correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2373 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error parsing insert statement for table %s. |
| Long Text: | A parsing error occurred. |
| Repair Text: | From Oracle doc: Check the message following this parsing error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2374 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No more slots for read buffer queue. |
| Long Text: | There are no free read buffers. |
| Repair Text: | From Oracle doc: Use the READBUFFERS keyword in the loader to increase the number of read buffers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2375 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Record %s: Rejected - Error on table %s |
| Long Text: | The record indicated caused an Oracle error on insert. |
| Repair Text: | From Oracle doc: Determine the Oracle error and correct the record. The offending column(s) are not known. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2376 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or redundant resource |
| Long Text: | A resource that is not defined or that is specified twice appears in the CREATE or ALTER PROFILE statement. |
| Repair Text: | From Oracle doc: Define the resource before issuing a CREATE or ALTER PROFILE command. Also check the statement to see that each resource is listed only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2377 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid resource limit |
| Long Text: | An invalid resource limit of 0 was specified. |
| Repair Text: | From Oracle doc: Specify a resource limit greater than 0. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2378 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate resource name %s |
| Long Text: | The same resource was specified twice in a CREATE or ALTER PROFILE statement. |
| Repair Text: | From Oracle doc: Issue the statement again, carefully checking that each resource is used only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2379 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | profile %s already exists |
| Long Text: | An attempt was made to create a profile that already exists. |
| Repair Text: | From Oracle doc: Create the profile with a name not already used by another profile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2380 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | profile %s does not exist |
| Long Text: | An attempt was made to assign a user to a non-existent profile. |
| Repair Text: | From Oracle doc: Assign the user to an existing profile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2381 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop PUBLIC_DEFAULT profile |
| Long Text: | An attempt was made to drop the PUBLIC_DEFAULT profile. |
| Repair Text: | From Oracle doc: The PUBLIC_DEFAULT profile cannot be dropped. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2382 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | profile %s has users assigned, cannot drop without CASCADE |
| Long Text: | An attempt was made to drop a profile that had users assigned to it without using the CASCADE option of the DROP PROFILE statement. A profile that has users assigned to it cannot be dropped, unless the CASCADE option is specified. CASCADE reassigns users to the PUBLIC_DEFAULT profile before dropping the profile. |
| Repair Text: | From Oracle doc: To reassign all users to the PUBLIC_DEFAULT profile, issue the DROP PROFILE statement with the CASCADE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2383 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal cost factor |
| Long Text: | A negative value or UNLIMITED cost was specified for this resource in the ALTER RESOURCE COST statement. |
| Repair Text: | From Oracle doc: Only positive integer values can be specified for resources in the ALTER RESOURCE COST statement. Issue the statement again, using a positive integer value for each resource specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2390 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded COMPOSITE_LIMIT, you are being logged off |
| Long Text: | The COMPOSITE_LIMIT for the profile is exceeded. That is, the weighted sum of the connection time, logical reads per session, CPU usage per session, and private SGA space used during the session exceeded the limit set by the COMPOSITE_LIMIT clause set in the user profile. |
| Repair Text: | From Oracle doc: If this happens often, ask the database administrator to raise the COMPOSITE_LIMIT of the user profile, or determine which resource is used the most and raise the limit on that resource. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2391 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded simultaneous SESSIONS_PER_USER limit |
| Long Text: | An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSIONS_PER_USER clause of the user profile. |
| Repair Text: | From Oracle doc: End one or more concurrent sessions or ask the database administrator to increase the SESSIONS_PER_USER limit of the user profile. For more information about SESSIONS_PER_USER and the database administrator's specific tasks of adjusting concurrent sessions, see Oracle8i SQL Reference and the Oracle8i Administrator's Guide |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2392 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded session limit on CPU usage, you are being logged off |
| Long Text: | An attempt was made to exceed the maximum CPU usage allowed by the CPU_PER_SESSION clause of the user profile. |
| Repair Text: | From Oracle doc: If this happens often, ask the database administrator to increase the CPU_PER_SESSION limit of the user profile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2393 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded call limit on CPU usage |
| Long Text: | An attempt was made to exceed the maximum CPU time for a call, a parse, execute, or fetch, allowed by the CPU_PER_CALL clause of the user profile. |
| Repair Text: | From Oracle doc: If this happens often, ask the database administrator to increase the CPU_PER_CALL limit of the user profile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2394 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded session limit on IO usage, you are being logged off |
| Long Text: | An attempt was made to exceed the maximum I/O allowed by the LOGICAL_READS_PER_SESSION clause of the user profile. |
| Repair Text: | From Oracle doc: If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_SESSION limit of the user profile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2395 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded call limit on IO usage |
| Long Text: | An attempt was made to exceed the maximum I/O for a call, a parse, execute, or fetch, allowed by the LOGICAL_READS_PER_CALL clause of the user profile. |
| Repair Text: | From Oracle doc: If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_CALL limit of the user profile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2396 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded maximum idle time, please connect again |
| Long Text: | A user has exceeded the maximum time allowed to remain idle. |
| Repair Text: | From Oracle doc: The user must reconnect to the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2397 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded PRIVATE_SGA limit, you are being logged off |
| Long Text: | This error occurs only when using a multi-threaded server. |
| Repair Text: | From Oracle doc: Contact the database administrator to expand the PRIVATE_SGA limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2398 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded procedure space usage |
| Long Text: | Stored procedures used up too much space in the SYSTEM tablespace. |
| Repair Text: | From Oracle doc: Use fewer stored procedures or add an additional file to the system tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2399 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded maximum connect time, you are being logged off |
| Long Text: | A user has exceeded the maximum time allowed to be connected to the database. |
| Repair Text: | From Oracle doc: The user must reconnect to the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot EXPLAIN view owned by another user |
| Long Text: | The view specified in the SQL statement belongs to another user and cannot be explained. |
| Repair Text: | From Oracle doc: Create a view with the same definition that belongs to current user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PLAN_TABLE not found |
| Long Text: | The table used by EXPLAIN to store row source information does not exist in the current schema. |
| Repair Text: | From Oracle doc: Create a plan table in the current schema or use the INTO clause of the statement to put the results of the explain command in an existing plan table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | plan table does not have correct format |
| Long Text: | The explicit plan table does not have the appropriate field definitions. |
| Repair Text: | From Oracle doc: Redefine the plan table to have the appropriate field definitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified plan table not found |
| Long Text: | The specified plan table does cannot be found. |
| Repair Text: | From Oracle doc: Create the specified plan table or use an existing plan table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2420 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing schema authorization clause |
| Long Text: | The AUTHORIZATION clause is missing from a create schema statement. |
| Repair Text: | From Oracle doc: Proceed the schema authorization identifier with the AUTHORIZATION keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2421 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid schema authorization identifier |
| Long Text: | One of the following: The schema authorization identifier is not recognized. An attempt was made to use a schema authorization identifier for a user while not connected as that user. |
| Repair Text: | From Oracle doc: If the cause is an unrecognized identifier, then use an existing identifier. connected with a different user name, then disconnect and connect to the correct user name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2422 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid schema element |
| Long Text: | A statement other than a CREATE TABLE, CREATE VIEW, or GRANT appears in a CREATE SCHEMA statement. |
| Repair Text: | From Oracle doc: See Oracle8i SQL Reference or the valid elements of the CREATE SCHEMA statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2423 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | schema name does not match schema authorization identifier |
| Long Text: | A table definition with a schema name prepended to the table name does not match the schema name provided in the AUTHORIZATION clause of a CREATE SCHEMA STATEMENT. |
| Repair Text: | From Oracle doc: Check that the schema names match the one given in the CREATE SCHEMA statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2424 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | potential circular view references or unknown referenced tables |
| Long Text: | The CREATE SCHEMA statement contains a view that depends on other views contained in the CREATE SCHEMA statement, or they contain references to non-existing tables. |
| Repair Text: | From Oracle doc: Create the dependent views in a separate CREATE SCHEMA statement and ensure that all referenced tables are either defined in the CREATE SCHEMA statement or exist outside the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2425 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | create table failed |
| Long Text: | A CREATE TABLE statement failed in the CREATE SCHEMA statement. |
| Repair Text: | From Oracle doc: The cause for failure will be presented below this message. Follow the appropriate actions as suggested by the subsequent messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2426 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | privilege grant failed |
| Long Text: | A GRANT statement failed in the CREATE SCHEMA statement. |
| Repair Text: | From Oracle doc: The cause for failure will be presented below this message. Follow appropriate actions, as suggested by the subsequent messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2427 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | create view failed |
| Long Text: | A CREATE VIEW statement failed in the CREATE SCHEMA statement. |
| Repair Text: | From Oracle doc: The cause for failure will be presented below this message. Follow appropriate actions, as suggested by the subsequent messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2428 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not add foreign key reference |
| Long Text: | Oracle could not add a foreign key reference because of an error in the declaration. Either the referenced table does not exist or the table does not have a unique key. |
| Repair Text: | From Oracle doc: Check that the referenced table exists and/or has a unique key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2429 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop index used for enforcement of unique/primary key |
| Long Text: | An attempt was made to drop an index that is being used as the enforcement mechanism for a unique or primary key. |
| Repair Text: | From Oracle doc: Drop the integrity constraint instead of dropping the index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot enable constraint (%s) - no such constraint |
| Long Text: | The named constraint does not exist for this table. |
| Repair Text: | From Oracle doc: Check that a constraint exists before trying to enable it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot disable constraint (%s) - no such constraint |
| Long Text: | The named constraint does not exist for this table. |
| Repair Text: | From Oracle doc: Check that a constraint exists before trying to disable it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot enable primary key - primary key not defined for table |
| Long Text: | An attempt was made to enable a primary key that is not defined for the table. |
| Repair Text: | From Oracle doc: Add a primary key definition for the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot disable primary key - primary key not defined for table |
| Long Text: | An attempt was made to disable a primary key that is not defined for the table. |
| Repair Text: | From Oracle doc: Check that a primary key exists before trying to disable it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2434 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot enable unique(%s) - unique key not defined for table |
| Long Text: | An attempt was made to enable a unique key that is not defined for the table. |
| Repair Text: | From Oracle doc: Check that a unique key exists before trying to enable it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2435 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot disable unique(%s) - unique key not defined for table |
| Long Text: | An attempt was made to disable a unique key that is not defined for the table. |
| Repair Text: | From Oracle doc: Check that a unique key exists before trying to disable it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | date or system variable wrongly specified in CHECK constraint |
| Long Text: | An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century. |
| Repair Text: | From Oracle doc: Completely specify the date constant or system variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot validate (%s.%s) - primary key violated |
| Long Text: | An attempt was made to validate a primary key with duplicate values or null values. |
| Repair Text: | From Oracle doc: Remove the duplicates and null values before enabling a primary key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Column check constraint cannot reference other columns |
| Long Text: | An attempt was made to define a column check constraint that references another column. |
| Repair Text: | From Oracle doc: Define it as a table check constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2439 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unique index on a deferrable constraint is not allowed |
| Long Text: | An attempt was made to enable a deferrable primary key/unique constraint that has an existing unique index on the constraint columns. |
| Repair Text: | From Oracle doc: Drop the index on the constraint columns or make the constraint not deferrable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Create as select with referential constraints not allowed |
| Long Text: | Integrity constraints on a table cannot be created when creating the table using the CREATE TABLE... AS SELECT... form. |
| Repair Text: | From Oracle doc: First, create the table, and then alter the table to add the desired integrity constraints. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot drop nonexistent primary key |
| Long Text: | An attempt was made to drop the primary key constraint on a table, but there is no primary key constraint on this table. |
| Repair Text: | From Oracle doc: Ensure the correct table name is entered in the statement. Otherwise, no action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2442 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot drop nonexistent unique key |
| Long Text: | An attempt was made to drop a unique key constraint for a column that does not have a unique key constraint. |
| Repair Text: | From Oracle doc: Make certain the correct column name was entered. Otherwise, no action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot drop constraint - nonexistent constraint |
| Long Text: | An attempt was made to drop a constraint that does not exist. |
| Repair Text: | From Oracle doc: Make certain the constraint and table name are correct and attempt the procedure again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot resolve referenced object in referential constraints |
| Long Text: | An attempt was made to define a foreign key with a reference to a schema object that cannot be resolved to a base table reference. |
| Repair Text: | From Oracle doc: Define referential constraints only with schema objects resolving to a base table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2445 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Exceptions table not found |
| Long Text: | The explicitly or implicitly declared exceptions table does not exist. |
| Repair Text: | From Oracle doc: If the correct exceptions table name was used, then create the table and retry the enable command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CREATE TABLE ... AS SELECT failed - check constraint violated |
| Long Text: | An attempt was made to use a CREATE TABLE ... AS SELECT statement when some rows violated one or more CHECK constraints. |
| Repair Text: | From Oracle doc: Do not select rows that violate constraints. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2447 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot defer a constraint that is not deferrable |
| Long Text: | An attempt was made to defer a nondeferrable constraint. |
| Repair Text: | From Oracle doc: Drop the constraint and create a new one that is deferrable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2448 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | constraint does not exist |
| Long Text: | The named constraint does not exist. |
| Repair Text: | From Oracle doc: Choose a constraint that does exist or do not perform this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unique/primary keys in table referenced by foreign keys |
| Long Text: | An attempt was made to drop a table with unique or primary keys referenced by foreign keys in another table. |
| Repair Text: | From Oracle doc: Before performing the above operations the table, drop the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam"; |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2450 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid hash option - missing keyword IS |
| Long Text: | Missing IS keyword. |
| Repair Text: | From Oracle doc: Specify HASH IS option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate HASHKEYS specification |
| Long Text: | The HASHKEYS option is specified more than once. |
| Repair Text: | From Oracle doc: Only specify the HASHKEYS option once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid HASHKEYS option value |
| Long Text: | The specified HASHKEYS option must be an integer value. |
| Repair Text: | From Oracle doc: Specify an appropriate value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate HASH IS specification |
| Long Text: | The HASH IS option is specified more than once. |
| Repair Text: | From Oracle doc: only specify the HASH IS option once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2454 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Number of hash keys per block (%s) exceeds maximum of %s |
| Long Text: | The SIZE argument is too small. |
| Repair Text: | From Oracle doc: Increase the SIZE argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2455 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The number of cluster key column must be 1 |
| Long Text: | When specifying the HASH IS option, the number of key columns must be 1. |
| Repair Text: | From Oracle doc: Either do not specify the HASH IS option or reduce the number of key columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2456 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The HASH IS column specification must be NUMBER(*,0) |
| Long Text: | The column specification must specify an integer. |
| Repair Text: | From Oracle doc: Specify the column definition as type NUMBER(precision, 0). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2457 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The HASH IS option must specify a valid column |
| Long Text: | The HASH IS column name is not specified in the cluster definition. |
| Repair Text: | From Oracle doc: Specify a valid column name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2458 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | HASHKEYS must be specified for a HASH CLUSTER |
| Long Text: | The HASHKEYS option must be specified when creating a HASH CLUSTER. |
| Repair Text: | From Oracle doc: Specify the HASHKEYS option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2459 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Hashkey value must be a positive integer |
| Long Text: | The value of the hash key was not a positive number. |
| Repair Text: | From Oracle doc: Specify a positive integer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2460 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Inappropriate index operation on a hash cluster |
| Long Text: | An attempt to create a cluster index was issued on a hash cluster. |
| Repair Text: | From Oracle doc: Do not attempt to create such an index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2461 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Inappropriate use of the INDEX option |
| Long Text: | This option is only valid for non hash clusters. |
| Repair Text: | From Oracle doc: Do not specify this option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2462 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Duplicate INDEX option specified |
| Long Text: | The INDEX option is specified more than once. |
| Repair Text: | From Oracle doc: Only specify the INDEX option once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2463 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Duplicate HASH IS option specified |
| Long Text: | The HASH IS option is specified more than once. |
| Repair Text: | From Oracle doc: Only specify the HASH IS option once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2464 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cluster definition can not be both HASH and INDEX |
| Long Text: | The cluster can either be a hash or indexed cluster, not both. |
| Repair Text: | From Oracle doc: Remove either the HASH IS or INDEX options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2465 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Inappropriate use of the HASH IS option |
| Long Text: | This option is only valid for clusters. |
| Repair Text: | From Oracle doc: Do not specify this option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2466 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The SIZE option is not allow to be altered for HASH CLUSTERS |
| Long Text: | The SIZE cannot be changed once the hash cluster has been created. |
| Repair Text: | From Oracle doc: Do not specify this option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2467 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Column referenced in expression not found in cluster definition |
| Long Text: | A column in the hash is expression was not present in cluster definition. |
| Repair Text: | From Oracle doc: Re-create the cluster and correct the error in hash expression. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2468 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Constant or system variable wrongly specified in expression |
| Long Text: | A constant or system variable was specified in the hash expression. |
| Repair Text: | From Oracle doc: Re-create the cluster and correct the error in hash expression. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2469 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Hash expression does not return an Oracle Number. |
| Long Text: | Result of evaluating hash expression is not an Oracle Number. |
| Repair Text: | From Oracle doc: Re-create the cluster and correct the error in hash expression. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2470 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression. |
| Long Text: | TO_DATE, USERENV and SYSDATE are not allowed in hash expressions. |
| Repair Text: | From Oracle doc: Re-create the cluster and correct the error in hash expression. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2471 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression. |
| Long Text: | SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expressions. |
| Repair Text: | From Oracle doc: Re-create the cluster and remove the offending keywords. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2472 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL functions not allowed in hash expressions |
| Long Text: | A PL/SQL function was used in the hash expression. |
| Repair Text: | From Oracle doc: Re-create the cluster and remove the PL/SQL function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2473 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error while evaluating the cluster's hash expression. |
| Long Text: | An error occurred while evaluating the clusters hash expression. |
| Repair Text: | From Oracle doc: Correct the query and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2474 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Fixed hash area extents used (%s) exceeds maximum allowed (%s) |
| Long Text: | The number of extents required for creating the fixed hash area exceeds the maximum number allowed. |
| Repair Text: | From Oracle doc: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2475 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum cluster chain block count of %s has been exceeded |
| Long Text: | The number of blocks in a cluster chain exceeds the maximum number allowed. |
| Repair Text: | From Oracle doc: Increase SIZE parameter in CREATE CLUSTER statement or reconsider suitability of cluster key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2476 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not create index due to parallel direct load on table |
| Long Text: | A parallel direct load is occurring to the specified table. |
| Repair Text: | From Oracle doc: Retry statement after load is complete. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2477 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not perform parallel direct load on object %s |
| Long Text: | A parallel direct load is not possible because an index is being created on the table. |
| Repair Text: | From Oracle doc: Retry load after index creation is complete. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2478 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | merge into base segment would overflow MAXEXTENTS limit |
| Long Text: | Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temporary and base segments. |
| Repair Text: | From Oracle doc: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2479 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while translating file name for parallel load |
| Long Text: | An invalid file name was specified to load data into. |
| Repair Text: | From Oracle doc: Specify a valid database file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2480 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many event classes specified for events |
| Long Text: | Illegal trace enable string. |
| Repair Text: | From Oracle doc: Enter a legal trace enable control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2481 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many ID ranges specified for events |
| Long Text: | Illegal trace enable string. |
| Repair Text: | From Oracle doc: Enter a legal trace enable control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2482 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Specified an event class but gave no events |
| Long Text: | Illegal trace enable string. |
| Repair Text: | From Oracle doc: Enter a legal trace enable control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2483 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Illegal ID value specified for events |
| Long Text: | Illegal trace enable string. |
| Repair Text: | From Oracle doc: Enter a legal trace enable control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2485 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Low ID value is greater than high ID value |
| Long Text: | Bad file name given in TRACE_DEST initialization parameter. |
| Repair Text: | From Oracle doc: Specify a valid name in the TRACE_DEST initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2486 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error in file %s. Check trace_dest INIT.ORA parm |
| Long Text: | Bad file name given in TRACE_DEST initialization parameter. |
| Repair Text: | From Oracle doc: Specify a valid name in the TRACE_DEST initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2487 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error in writing file name %s. Check trace_dest INIT.ORA parm |
| Long Text: | Bad file name given in TRACE_DEST initialization parameter. |
| Repair Text: | From Oracle doc: Specify a valid name in the TRACE_DEST initialization parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2489 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trace_block_size (%s) must be divisable by %s |
| Long Text: | The initialization parameter TRACE_BLOCK_SIZE was incorrectly set. |
| Repair Text: | From Oracle doc: Change the initialization parameter and restart. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2490 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing required file size in RESIZE clause |
| Long Text: | No value was specified for the RESIZE clause. |
| Repair Text: | From Oracle doc: Use the correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2491 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing required keyword ON or OFF in AUTOEXTEND clause |
| Long Text: | The keyword ON or OFF was not specified for the AUTOEXTEND clause. |
| Repair Text: | From Oracle doc: Use the correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2492 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing required file block increment size in NEXT clause |
| Long Text: | No value was specified for the NEXT clause. |
| Repair Text: | From Oracle doc: Use the correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2493 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid file increment size in NEXT clause |
| Long Text: | A non-integer value was used for the NEXT clause of the DATAFILE list. |
| Repair Text: | From Oracle doc: Use the correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2494 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or missing maximum file size in MAXSIZE clause |
| Long Text: | UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value. |
| Repair Text: | From Oracle doc: Use the correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2495 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot resize file %s, tablespace %s is read only |
| Long Text: | An attempt was made to resize a datafile in a tablespace that is read only. |
| Repair Text: | From Oracle doc: Change the tablespace to read/write and retry the resize operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2700 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnoraenv: error translating ORACLE_SID |
| Long Text: | Two-task driver could not find the value of ORACLE_SID in the environment. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_SID environment variable has been properly set and exported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnoraenv: error translating oracle image name |
| Long Text: | ORACLE_HOME environment variable not set. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME environment variable has been properly set and exported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnoraenv: error translating orapop image name |
| Long Text: | ORACLE_HOME environment variable not set. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME environment variable has been properly set and exported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpopipe: pipe creation failed |
| Long Text: | The pipe driver failed to create pipes for communications with the ORAPOP process. |
| Repair Text: | From Oracle doc: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osndopop: fork failed |
| Long Text: | The two-task driver could not fork ORAPOP. |
| Repair Text: | From Oracle doc: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpol: polling of communication channel failed |
| Long Text: | The pipe driver failed while polling the communications channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnshs: host name too long |
| Long Text: | The length of your host-string specified by the TWO_TASK environment variable exceeds the Oracle system-imposed limit. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2707 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnacx: cannot allocate context area |
| Long Text: | The invoked UNIX two-task driver could not allocate heap space for the context area. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnrntab: connect to host failed, unknown ORACLE_SID |
| Long Text: | The invoked UNIX two-task driver failed to find an entry in ORATAB for the SID you supplied. |
| Repair Text: | From Oracle doc: First, check whether you have read access to ORATAB, and see if the desired sid is there. Add an entry to ORATAB for the desired SID, if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpop: pipe creation failed |
| Long Text: | The pipe driver failed to create pipes for two-task communications with the Oracle shadow process. |
| Repair Text: | From Oracle doc: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2710 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpop: fork failed |
| Long Text: | The pipe driver could not fork the Oracle shadow process. |
| Repair Text: | From Oracle doc: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2711 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpvalid: write to validation channel failed |
| Long Text: | The pipe driver failed to write to the ORAPOP process. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2712 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpop: malloc failed |
| Long Text: | The pipe driver failed to allocate enough heap space for its context area buffers. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2713 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnprd: message receive failure |
| Long Text: | The pipe driver failed to read a message from the communications channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2714 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpwr: message send failure |
| Long Text: | The pipe driver failed to write a message to the communications channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2715 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpgetbrkmsg: message from host had incorrect message type |
| Long Text: | The pipe driver received a message having an unrecognizable message type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2716 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpgetdatmsg: message from host had incorrect message type |
| Long Text: | The Pipe driver received a message having an unrecognizable message type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2717 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpfs: incorrect number of bytes written |
| Long Text: | The Pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2718 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnprs: reset protocol error |
| Long Text: | The two-task driver could not reset the connection. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2719 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfop: fork failed |
| Long Text: | The fast driver could not fork the Oracle shadow process. |
| Repair Text: | From Oracle doc: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2720 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfop: shmat failed |
| Long Text: | When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accommodate the buffer. |
| Repair Text: | From Oracle doc: Try invoking the Fast driver later, or use the default attach address. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2721 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnseminit: cannot create semaphore set |
| Long Text: | The Fast driver failed to get a semaphore set. |
| Repair Text: | From Oracle doc: The system-imposed limit on semaphores or semaphore identifiers may have been exceeded. Read the returned operating system error code and check with your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2722 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpui: cannot send break message to orapop |
| Long Text: | The Pipe driver could not send a break message to ORAPOP. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2723 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpui: cannot send break signal |
| Long Text: | The Pipe driver could not send a break message to the Oracle shadow process. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2724 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpbr: cannot send break message to orapop |
| Long Text: | The Pipe driver could not send a break message to ORAPOP. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2725 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpbr: cannot send break signal |
| Long Text: | The Pipe driver could not send a break message to the Oracle shadow process. |
| Repair Text: | From Oracle doc: Kill system call failed. Check the error code (errno) and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2726 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpop: access error on oracle executable |
| Long Text: | The Pipe driver could not access the Oracle executable. |
| Repair Text: | From Oracle doc: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2727 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpop: access error on orapop executable |
| Long Text: | The Pipe driver could not access the ORAPOP executable. |
| Repair Text: | From Oracle doc: Check the permissions on the ORAPOP executable and each component of the ORACLE_HOME/bin path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2728 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfop: access error on oracle executable |
| Long Text: | The Fast driver could not access the Oracle executable. |
| Repair Text: | From Oracle doc: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2729 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osncon: driver not in osntab |
| Long Text: | The driver you have specified is not supported. |
| Repair Text: | From Oracle doc: Check with your database administrator which drivers are supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2730 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnrnf: cannot find user logon directory |
| Long Text: | The driver you have specified could not find your logon directory while searching for your local .SQLNET file. |
| Repair Text: | From Oracle doc: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure that your UID and home directory are correct in the /etc/passwd file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2731 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnrnf: malloc of buffer failed |
| Long Text: | The specified driver could not find enough heap space to MALLOC a buffer. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2732 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnrnf: cannot find a matching database alias |
| Long Text: | Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet. |
| Repair Text: | From Oracle doc: Create the alias in a file called .sqlnet in the home directory for personal use, or have system administrator create the alias in /etc/sqlnet for system-wide use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2733 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnsnf: database %s too long |
| Long Text: | While converting a database alias to a database ID, the resulting database ID string exceeded the Oracle system-imposed limit. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2734 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnftt: cannot reset shared memory permission |
| Long Text: | The Fast driver was unable to reset shared memory permissions. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2735 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfpm: cannot create shared memory segment |
| Long Text: | The Fast driver failed to create a shared memory segment for two-task communication. |
| Repair Text: | From Oracle doc: Check whether the system-imposed limit on shared memory identifiers has already been reached for your system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2736 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfpm: illegal default shared memory address |
| Long Text: | The Fast driver failed to establish a default shared memory address. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2737 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpcl: cannot tell orapop to exit |
| Long Text: | The Pipe driver failed to send ORAPOP the command to exit. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2738 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpwrtbrkmsg: incorrect number of bytes written |
| Long Text: | The pipe driver apparently sent an incomplete break message. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2739 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osncon: host alias is too long |
| Long Text: | The alias used for a SQLNET host is longer than 161 characters. |
| Repair Text: | From Oracle doc: Use a shorter alias. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2750 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfsmmap: cannot open shared memory file ?/dbs/ftt_pid.dbf |
| Long Text: | The Fast driver failed to create a shared memory file for two-task communication. |
| Repair Text: | From Oracle doc: Check the permissions on the directory ?/dbs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2751 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfsmmap: cannot map shared memory file |
| Long Text: | The Fast driver failed to map a shared memory file for two-task communication. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2752 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfsmmap: illegal shared memory address |
| Long Text: | The Fast driver failed to attach shared memory at the expected location. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2753 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfsmmap: cannot close shared memory file |
| Long Text: | The Fast driver cannot close the shared memory file. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2754 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfsmmap: cannot change shared memory inheritence |
| Long Text: | The Fast driver could not alter the inheritance attributes of the shared memory. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2755 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfsmcre: cannot create chared memory file ?/dbs/ftt_pid.dbf |
| Long Text: | The Fast driver failed to create a file for shared memory. |
| Repair Text: | From Oracle doc: Check the permissions on the directory ?/dbs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2756 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfsmnam: name translation failure |
| Long Text: | The Fast driver encountered an error translating the shared memory file name ?/dbs/ftt_pid.dbf. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2757 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnfop: fork_and_bind failed |
| Long Text: | The Fast driver failed to fork a process onto the desired cluster and node number. |
| Repair Text: | From Oracle doc: Check the desired node number in sercose[0] and cluster ID in sercose[1]. If these seem valid, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2758 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Allocation of internal array failed |
| Long Text: | The package was unable to allocate memory for an array because the system ran out of memory. |
| Repair Text: | From Oracle doc: Either reclaim memory by killing other processes or restart the machine with more memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2759 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Not enough request descriptors available |
| Long Text: | All of the package's request descriptors are in use performing other requests. |
| Repair Text: | From Oracle doc: Either wait until enough requests are done, or shut the package down and re-initialize it with more request descriptors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2760 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Client close of file failed. |
| Long Text: | The client was unable to close a file after forking the servers. |
| Repair Text: | From Oracle doc: This is a system problem; contact your System Administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2761 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File number to be canceled is negative. |
| Long Text: | The file number contained with the SFIOV structure is less than zero. |
| Repair Text: | From Oracle doc: This may be a programming error. If it is not, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2762 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file number to be cancelled is greater than the maximum. |
| Long Text: | The file number contained with the SFIOV structure is greater than the maximum. |
| Repair Text: | From Oracle doc: This may be a programming error. If it is not, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2763 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to cancel at least one request |
| Long Text: | No requests were found that could be cancelled. |
| Repair Text: | From Oracle doc: This error can occur if all the requests dealing with that file number have already been filled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2764 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid package mode |
| Long Text: | The mode of the package can only be parallel or duplex. |
| Repair Text: | From Oracle doc: See SFA.H for the correct values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2765 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid maximum number of servers |
| Long Text: | The number of servers given was less than or equal to zero. |
| Repair Text: | From Oracle doc: Use a number greater than zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2766 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid maximum of request descriptors |
| Long Text: | The number of request descriptors was less than or equal to zero. |
| Repair Text: | From Oracle doc: Use a number greater than zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2767 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Less than one request descriptor was allocated per server |
| Long Text: | The package requires that the number of request descriptors be greater than or equal to the number of servers used. |
| Repair Text: | From Oracle doc: Use a higher number |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2768 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Maximum number of files is invalid |
| Long Text: | The maximum number of files to be used by the package was less than or equal to zero. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2769 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Setting of handler for SIGTERM failed |
| Long Text: | The package was unable to set up handling by the server for the termination signal. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2770 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Total number of blocks is invalid |
| Long Text: | The total number of blocks to be allocated for use by the package was not greater than zero. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2771 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Illegal request time out value |
| Long Text: | The number was not a positive number. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2772 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid maximum server idle time |
| Long Text: | The time given was not a positive number. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2773 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid maximum client wait time |
| Long Text: | The time given was not a positive number. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2774 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid request list latch time out value |
| Long Text: | The time given was not a positive number. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2775 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid request done signal |
| Long Text: | The signal number was not a positive number. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2776 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Value for request done signal exceeds maximum |
| Long Text: | The value sent to the package for use as the "request done" signal exceeds the maximum allowed by the operating system. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2777 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Stat failed on log directory |
| Long Text: | The package was unable to get information about the directory in which the log files are to reside. |
| Repair Text: | From Oracle doc: Check the permissions on the directory or use a different directory name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2778 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Name given for the log directory is invalid |
| Long Text: | The name given for the directory in which the logs are to be kept does not correspond to a directory. |
| Repair Text: | From Oracle doc: Use a different name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2779 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Stat failed on core dump directory |
| Long Text: | The package was unable to get information about the directory into which the servers are to dump core in the event of an exception. |
| Repair Text: | From Oracle doc: Check the permissions on the directory or use a different directory name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2780 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Name given for the core dump directory is invalid |
| Long Text: | The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory. |
| Repair Text: | From Oracle doc: Use a different name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2781 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid value given for the timing wanted flag |
| Long Text: | The value given was not TRUE or FALSE. |
| Repair Text: | From Oracle doc: Specify TRUE or FALSE for the timing wanted flag. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2782 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Both read and write functions were not specified |
| Long Text: | To ensure that the functions act symmetrically, pointers to both the read and write functions must be given. |
| Repair Text: | From Oracle doc: Either specify both functions or specify neither. The package will supply its own functions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2783 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Both post and wait functions were not specified |
| Long Text: | To ensure that the functions act symmetrically, pointers to both the posting and waiting functions must be given. |
| Repair Text: | From Oracle doc: Either specify both functions or specify neither. The package will supply its own functions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2784 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid shared memory ID specified |
| Long Text: | The ID of the segment specified for use as the shared buffer region was invalid. |
| Repair Text: | From Oracle doc: Use a different ID, or let the package specify its own. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2785 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid shared memory buffer size |
| Long Text: | The size given for the shared memory segment to be used as the shared buffer region was less than or equal to zero. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2786 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Size needed for shared region is greater than segment size |
| Long Text: | The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the size needed. The second is the size of the segment. |
| Repair Text: | From Oracle doc: Use a larger size segment or let the package allocate its own. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2787 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to allocate memory for segment list |
| Long Text: | The package cannot allocate memory for an internal segment list because the system has run out of memory. The "additional information" field is the amount of memory that the package attempted to allocate. |
| Repair Text: | From Oracle doc: Close some processes or contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2788 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to find kernel process pointer in async process array |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2789 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Maximum number of files reached |
| Long Text: | The maximum number of files that can be used for asynchronous I/O has been reached. |
| Repair Text: | From Oracle doc: Shut down the servers and re-initialize the package with a higher number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2790 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File name is too long |
| Long Text: | The length of the name of a file that is being opened for asynchronous I/O is longer than the maximum. The "additional information" field is the maximum length. |
| Repair Text: | From Oracle doc: Use a shorter name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2791 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to open file for use with asynchronous I/O |
| Long Text: | The package could not open file for some reason. |
| Repair Text: | From Oracle doc: Check the file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2792 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to fstat() a file being used for asynchronous I/O. |
| Long Text: | The fstat(2) call on a file being used for asynchronous I/O failed. |
| Repair Text: | From Oracle doc: Check the file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2793 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Close of asynchronous I/O failed. |
| Long Text: | The client was unable to close a file being used for asynchronous I/O. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2794 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Client unable to get key for shared memory |
| Long Text: | The client was unable to get a key so that it obtain shared memory for use with shared memory. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2795 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Request list is empty |
| Long Text: | The client was signalled by a server that it was done with a request but the "done" list was empty. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2796 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Done request is not in correct state |
| Long Text: | A request is not in the right state. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2797 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | No requests available |
| Long Text: | No free request descriptors are available. |
| Repair Text: | From Oracle doc: Wait until some requests are filled and then retry the request, or shut down the servers and initialize the package with a higher number of requests. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2798 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid number of requests |
| Long Text: | The number of operations sent to either SFARD() or SFAWRITE() is less than zero. This is a user programming error. |
| Repair Text: | From Oracle doc: Check the calling program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2799 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to arm signal handler |
| Long Text: | The arming of a signal handler for the "done" signal failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Requests timed out |
| Long Text: | Some of the requests for asynchronous input or output were not serviced in the required amount of time. |
| Repair Text: | From Oracle doc: If the load on the system is high, it is possible that the timeout limit is too low. Reset it with SFAINIT(). If the server processes are dying due to unexpected signals, this is an internal error, and Oracle Customer Support should be contacted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Operations timed out |
| Long Text: | Some asynchronous operations timed out in kernel mode. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No idle servers available in parallel mode |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Retrieval of current time failed |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Allocation of memory failed for log file name |
| Long Text: | The client was unable to allocated a buffer for the name of the log file. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2805 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to set handler for SIGTPA |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2806 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to set handler for SIGALRM |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2807 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Allocation of memory for I/O vectors failed. |
| Long Text: | The client was unable to allocate memory for the array of I/O vectors that the servers are to use. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2808 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Allocation of memory of open files array failed. |
| Long Text: | The client was unable to allocate memory for an array of flags that the servers are to use. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2809 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Jump buffer not valid |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to make temporary file name for memory mapped file |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to attach shared memory segment |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Bad attach address |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to make temporary file name in order to get key |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2814 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get shared memory |
| Long Text: | SHMGET(2) failed. |
| Repair Text: | From Oracle doc: Check the UNIX number. If you are unsure about what it means, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2815 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to attach shared memory |
| Long Text: | SHMAT(2) failed. |
| Repair Text: | From Oracle doc: Check the UNIX number. If you are unsure about what it means, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to kill a process |
| Long Text: | A server did not die after being sent a kill signal. |
| Repair Text: | From Oracle doc: The process may be a runaway; contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2817 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Read failed |
| Long Text: | A server could not read a requested amount of data. |
| Repair Text: | From Oracle doc: Check the call to SFARD(). An incorrect file descriptor may have been sent to SFARD(). The number in the "additional information" field is the starting block number of the data segment being read in. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2818 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Less than the number of blocks requested was read in |
| Long Text: | A server could not read in the request amount of data. The first number in the "additional information" field is the block number being read in. The second is the actual number of bytes that was read in. This is a programming error. |
| Repair Text: | From Oracle doc: Check the calling program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2819 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Write failed |
| Long Text: | A server was unable to perform a write. The number in the "additional information" field is the starting block number of the data segment being written out. The first number in the "additional information" field is the block number being written out. The second is the actual number of bytes that was written out. The disk may have filled up. |
| Repair Text: | From Oracle doc: Check the UNIX error number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2820 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to write the requested number of blocks |
| Long Text: | A server could not write the requested amount of data out to disk. The disk may have run out of space. |
| Repair Text: | From Oracle doc: Check the UNIX error number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2821 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to read the requested number of blocks. |
| Long Text: | A server could not read the number of blocks that was requested. The end of the file may have been read. |
| Repair Text: | From Oracle doc: Check the file on disk. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2822 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid block offset |
| Long Text: | A server was unable to seek to the designated block. |
| Repair Text: | From Oracle doc: Check the UNIX error number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2823 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Buffer is not aligned. |
| Long Text: | The buffer on which an I/O is being done is not on the correct boundary. |
| Repair Text: | From Oracle doc: Check the calling program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2824 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Request free list is empty |
| Long Text: | The list from which the package allocates request descriptors is empty because all of the descriptors is in use. |
| Repair Text: | From Oracle doc: Wait until some become free, or initialize the package with a higher number of request descriptors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2825 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Request on free list was not free |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2826 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Illegal block size |
| Long Text: | A negative number was given for the I/O block size to be used by the asynchronous I/O package. This is a programming error. |
| Repair Text: | From Oracle doc: Use either a positive number or zero to get the default value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2827 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid file number |
| Long Text: | The file number upon which an operation is to done is either less than zero or greater than the maximum number of files than can be open. |
| Repair Text: | From Oracle doc: Since the calling program should not touch this number, this is a programming error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2828 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Segment free list is empty |
| Long Text: | No segments are available to allocated. |
| Repair Text: | From Oracle doc: Free some segments or shut down the package and re-initialize it with a higher number of segments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2829 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No segment of the proper size is available |
| Long Text: | No segment of the proper size is ready for use by the caller. |
| Repair Text: | From Oracle doc: Free some segments and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2830 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Segment could not be split - no free segments available |
| Long Text: | A segment that is larger than that desired could not be split because no free segment was available. |
| Repair Text: | From Oracle doc: Free some segments and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2831 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Segment deallocation failed - empty segment list |
| Long Text: | The caller attempted to deallocate a segment but the "in use" list was empty. This is a programming error. |
| Repair Text: | From Oracle doc: Check the calling program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2832 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Segment deallocation failed - segment not on list |
| Long Text: | The caller attempted to deallocate a segment that was not on the "in use" list. This is a programming error. |
| Repair Text: | From Oracle doc: Check the calling program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2833 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server was unable to close file |
| Long Text: | A server was unable to close a file being used for asynchronous I/O. |
| Repair Text: | From Oracle doc: See the UNIX error number for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2834 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server unable to open file |
| Long Text: | The server was unable to open a file for use with asynchronous I/O. |
| Repair Text: | From Oracle doc: Check the UNIX error number for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2835 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server unable to send signal to client |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2836 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to create temporary key file |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2837 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to unlink temporary file |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2838 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to arm signal handler for the alarm signal |
| Long Text: | The arming of a signal handler for the alarm signal failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2839 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Sync of blocks to disk failed. |
| Long Text: | The server was unable to flush its writes out to disk. |
| Repair Text: | From Oracle doc: Check the UNIX error number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2840 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Open of log file by client failed |
| Long Text: | The client process was unable to open its log file. |
| Repair Text: | From Oracle doc: Check the UNIX error number for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2841 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server died on start up |
| Long Text: | A server exited during its initialization process. |
| Repair Text: | From Oracle doc: Check the servers' logs for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2842 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Client unable to fork a server |
| Long Text: | The client could not spawn a server. A possible reason is that the operating system has reached its limit on the number of processes that it can spawn. |
| Repair Text: | From Oracle doc: Either reduce the number of servers that are to be used, or reconfigure the operating system so that it can handle more processes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2843 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid value for kernel flag |
| Long Text: | An illegal value was given for the kernel flag in the information structure. Only TRUE and FALSE are permitted. This is a programming error. |
| Repair Text: | From Oracle doc: Check the calling routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2844 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid value for the leave open flag |
| Long Text: | A value was given for the flag that determines whether a file is to be left open after the client checks it to see if the servers can use it. Only TRUE and FALSE are supported. This is a programming error. |
| Repair Text: | From Oracle doc: Check the calling routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2845 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid value for the timing wanted flag |
| Long Text: | A value was given for the flag that indicates that operations are to be timed out. Only TRUE and FALSE are supported. This is a programming error. |
| Repair Text: | From Oracle doc: Check the calling routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2846 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unkillable server |
| Long Text: | A server failed to respond to the termination signal. The first number is the number of the server. The second is its UNIX process number. This is an internal problem. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2847 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server did not terminate when posted |
| Long Text: | A server did not respond to a posted request to shut down. The first number is the number of the server. The second is its UNIX process number. This is an internal problem. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2848 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Asynchronous I/O package is not running |
| Long Text: | An operation using the asynchronous I/O package was attempted without first initializing the package using SFAINIT(). |
| Repair Text: | From Oracle doc: Call SFAINIT() before using the package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2849 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Read failed because of an error |
| Long Text: | A server could not read the requested amount of data from disk. |
| Repair Text: | From Oracle doc: Check the UNIX error number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2850 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File is closed |
| Long Text: | A file upon which an asynchronous I/O operation is to be performed has already been closed by the package. This is a programming error. |
| Repair Text: | From Oracle doc: Check the calling program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2851 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Request list is empty when it should not be |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2852 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid critical-section time out value |
| Long Text: | The time given was not a positive number. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2853 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid server list latch time out value |
| Long Text: | The time given was not a positive number. |
| Repair Text: | From Oracle doc: Use a positive number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2854 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid number of request buffers |
| Long Text: | The value given for DB_SLAVE_BUFFERS in your INIT.ORA file is less than 0. |
| Repair Text: | From Oracle doc: Use a number that is greater than or equal to 0. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2855 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Number of requests is less than the number of slaves |
| Long Text: | The value given for DB_SLAVE_BUFFERS in your INIT.ORA file is less than the number specified for the number of slaves, DB_SLAVES. |
| Repair Text: | From Oracle doc: Specify a number that is greater than that given for DB_SLAVES Alternatively, specify 0. The kernel will supply the appropriate number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2875 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpini: Unable to get shared memory for PGA |
| Long Text: | Stated in error code (errno). |
| Repair Text: | From Oracle doc: Resolve the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2876 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpini: Unable to attach to shared memory for PGA |
| Long Text: | Stated in error code (errno). |
| Repair Text: | From Oracle doc: Resolve the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2877 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpini: Unable to initialize memory protection |
| Long Text: | The ADSPCINIT program has not been executed. |
| Repair Text: | From Oracle doc: Execute the ADSCPINIT program as shown in your Installation and Users' Guide. If the problem persists, try restarting your computer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2878 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2o: Variable smpdidini overwritten |
| Long Text: | The variable SMPDIDINI was overwritten, probably by client code. |
| Repair Text: | From Oracle doc: Verify client code (for example, in Pro*C check for illegal memory access). If the problem occurs outside Single Task operation, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2879 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2o: Could not gain access to protected memory |
| Long Text: | This is an internal error, note error code in errno. |
| Repair Text: | From Oracle doc: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2880 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpini: Could not register PGA for protection |
| Long Text: | This is an internal error, note error code in errno. |
| Repair Text: | From Oracle doc: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2881 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2o: Could not revoke access to protected memory |
| Long Text: | This is an internal error, note error code in errno. |
| Repair Text: | From Oracle doc: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2882 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2o: Could not register SGA for protection |
| Long Text: | This is an internal error, note error code in errno. |
| Repair Text: | From Oracle doc: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-2899 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: Cannot create SGA with Extended Shared Memory feature |
| Long Text: | The environment variable EXTSHM was set before starting Oracle. |
| Repair Text: | From Oracle doc: Unset the environment variable EXTSHM and restart Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unimplemented feature |
| Long Text: | At attempt was made to use a feature that is not currently implemented. |
| Repair Text: | From Oracle doc: Do not attempt to use this feature at this time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operator not implemented |
| Long Text: | At attempt was made to use an operator that is not currently implemented. |
| Repair Text: | From Oracle doc: Do not attempt to use this operator at this time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3007 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | obsolete feature |
| Long Text: | An attempt was made to use a feature that is no longer supported. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter COMPATIBLE >= %s needed for %s |
| Long Text: | An attempt was made to use a feature for a later Oracle version than the setting of the initialization parameter, COMPATIBLE. |
| Repair Text: | From Oracle doc: Set COMPATIBLE to the value in the message (or higher), and retry the command, but be aware that this will limit your downgrade options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | communication area cannot be allocated; insufficient memory |
| Long Text: | An attempt to allocate stack space for communication purposes failed. This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal protocol error |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3106 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | fatal two-task communication protocol error |
| Long Text: | The communication path between Oracle and the user task has stopped. This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | oranet buffer underflow |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | oranet: ORACLE does not support this interface version |
| Long Text: | The version of Oracle connected to via Net8 does not support this version of the Net8 protocol. |
| Repair Text: | From Oracle doc: Upgrade the older version of Oracle and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | oranet buffer overflow |
| Long Text: | Data being transferred between the user program and Oracle overflowed the buffer space available. This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | oranet: ORACLE does not support this SQL version |
| Long Text: | The version of Oracle connected to via Net8 does not support the version of the Net8 protocol. |
| Repair Text: | From Oracle doc: Upgrade the older version of Oracle and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | break received on communication channel |
| Long Text: | A break was processed on the communications channel, but was not properly handled by Net8 software. This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a server linked as single-task cannot use SQL*Net |
| Long Text: | A statement containing a Net8t connect string was issued to the single-task server. For example, a database link was used in a SQL statement. |
| Repair Text: | From Oracle doc: Do not use Net8t connect strings in a single-task environment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | end-of-file on communication channel |
| Long Text: | An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the Net8, two task, software. This message could occur if the shadow two-task process associated with a Net8 connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down. In addition, this message could occur when ALTER SYSTEM KILL SESSION or ALTER SYSTEM DISCONNECT SESSION were issued with the IMMEDIATE qualifier because, in those cases, the client's connection to the database is terminated without waiting for the client to issue a request. |
| Repair Text: | From Oracle doc: If this message occurs during a connection attempt, check the setup files for the appropriate Net8 driver and confirm Net8 software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of customer support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not connected to ORACLE |
| Long Text: | A call to Oracle was attempted when no connection was established. Usually this happens because a user-written program has not logged on. It may happen if communication trouble causes a disconnection. In addition, this message could occur when ALTER SYSTEM KILL SESSION or ALTER SYSTEM DISCONNECT SESSION were issued with the IMMEDIATE qualifier because, in those cases, the client's connection to the database is terminated without waiting for the client to issue a request. |
| Repair Text: | From Oracle doc: Try again. If the message recurs and the program is user written, check the program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported network datatype or representation |
| Long Text: | A user bind or define, or an Oracle function, is not supported by this heterogeneous Net8 connection. |
| Repair Text: | From Oracle doc: Upgrade the older version of Oracle and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid buffer length passed to a conversion routine |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3117 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two-task save area overflow |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3118 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two-task coroutine has invalid state |
| Long Text: | This is an internal error message not usually issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two-task conversion routine: integer overflow |
| Long Text: | An integer value in an internal Oracle structure overflowed when being sent or received over a heterogeneous connection. This can happen when an invalid buffer length or too great a row count is specified. It usually indicates a bug in the user application. |
| Repair Text: | From Oracle doc: Check parameters to Oracle calls. If the problem recurs, reduce all integer parameters, column values not included, to less than 32767. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no interface driver connected - function not performed |
| Long Text: | This message occurs usually because the Net8 driver is not loaded into memory or there is a mismatch of the version of the driver. A user program linked with an obsolete library may also cause this message. Only programs provided by Oracle Corporation should use this interface. |
| Repair Text: | From Oracle doc: If the message occurred during use of a program provided by Oracle Corporation, contact customer support. If a user program caused the message, relink the program with current versions of the Oracle libraries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to close ORACLE-side window on user side |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation would block |
| Long Text: | The attempted operation cannot complete now. |
| Repair Text: | From Oracle doc: Retry the operation later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two-task internal error |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | client-server protocol violation |
| Long Text: | The application received a bad escape sequence from the server and may indicate a problem with the client application user code. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | network driver does not support non-blocking operations |
| Long Text: | A non-blocking operation was attempted and the network driver does not support non-blocking operations. |
| Repair Text: | From Oracle doc: Use default blocking operations or use a driver supporting non-blocking operations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no new operations allowed until the active operation ends |
| Long Text: | An attempt was made to execute a new operation before the active non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched. |
| Repair Text: | From Oracle doc: Execute the new operation after the non-blocking operation completes. If piecewise binds/defines were done, execute the new operation after all the pieces have been inserted or fetched. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection is in blocking mode |
| Long Text: | The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode. |
| Repair Text: | From Oracle doc: If non-blocking mode is required use appropriate OCI calls to change the mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3129 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the next piece to be inserted is required |
| Long Text: | The application performed a piecewise bind on a column. |
| Repair Text: | From Oracle doc: Provide the next piece of this bind variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3130 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the buffer for the next piece to be fetched is required |
| Long Text: | The application performed a piecewise define on the column. |
| Repair Text: | From Oracle doc: Provide the next buffer for the next piece to be retrieved. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3131 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an invalid buffer was provided for the next piece |
| Long Text: | The application either provided the length of the buffer for the next piece to be zero or provided a null pointer. |
| Repair Text: | From Oracle doc: Verify if the buffer pointer for the next piece is null or if the length is zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3135 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection lost contact |
| Long Text: | 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed out the connection. |
| Repair Text: | From Oracle doc: 1) Check if the server session was terminated. 2) Check if the timeout parameters are set properly in sqlnet.ora. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3136 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | WARNING: inbound connection timed out |
| Long Text: | Connection has timed out because of cluster interconnect failure or User Authentication has failed. |
| Repair Text: | From Oracle doc: Contact Oracle customer support |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the segment type specification is invalid |
| Long Text: | The segment type is not TABLE, INDEX, or CLUSTER. |
| Repair Text: | From Oracle doc: Use a correct segment type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the group number specification is invalid |
| Long Text: | The freelist group number is either negative or larger than the number of freelist groups in the segment. |
| Repair Text: | From Oracle doc: Use a correct group number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the scan limit specification is invalid |
| Long Text: | The scan limit does not have a positive integer value greater than the number of freelist groups in the segment. |
| Repair Text: | From Oracle doc: Use a correct scan limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | concurrent update activity makes space analysis impossible |
| Long Text: | High volume of user updates interfere with the space analysis. |
| Repair Text: | From Oracle doc: Retry the command or lock the underlying objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the segment type specification should indicate partitioning |
| Long Text: | A partition name was specified for the space analysis, but the object type does not indicate partitioning. |
| Repair Text: | From Oracle doc: Specify PARTITION in the segment type if the object is partitioned, Otherwise, omit the partition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition name is required when partitioned type is specified |
| Long Text: | A partition name was not specified for the space analysis, but the object type indicates partitioning. |
| Repair Text: | From Oracle doc: Specify a partition name if the object is partitioned. Otherwise, specify a non-partitioned type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum file size of (%s) blocks in AUTOEXTEND clause is out of range |
| Long Text: | The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed. |
| Repair Text: | From Oracle doc: Reduce the size and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartitioned type must be specified for composite object |
| Long Text: | A partition type is specified for the space analysis, but the object type indicates composite partitioning. |
| Repair Text: | From Oracle doc: Specify a subpartition name and a subpartition type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned type must be specified for a non-composite object |
| Long Text: | A subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning. |
| Repair Text: | From Oracle doc: Specify a partition name and a partition type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBMS_ADMIN_PACKAGE invalid file/block specification |
| Long Text: | The value of file number or block number is outside of limits or inconsistent. |
| Repair Text: | From Oracle doc: Fix the file number/block number value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBMS_ADMIN_PACKAGE invalid option specification |
| Long Text: | The value of one of the option parameters is incorrect. |
| Repair Text: | From Oracle doc: Fix the option value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The segment does not exist or is not in a valid state |
| Long Text: | The segment specified in the DBMS_SPACE_ADMIN operation does not or is not an state appropriate for this operation. |
| Repair Text: | From Oracle doc: Fix the segment specification, or put the segment in the appropriate state. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Temporary Segment cannot be created in locally-managed tablespace |
| Long Text: | An attempt was made to create a temporary segment for SORT/HASH/LOBS in a locally-managed permanent tablespace. |
| Repair Text: | From Oracle doc: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid Lob Segment Name for DBMS_SPACE package |
| Long Text: | The LOB segment specified in the DBMS_SPACE operation does not exist. |
| Repair Text: | From Oracle doc: Fix the segment specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File Size specified is smaller than minimum required |
| Long Text: | File size specified for add/resize datafile/temporary file does not allow for the minimum required of one allocation unit. |
| Repair Text: | From Oracle doc: Increase the specification for the file size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File Size specified for resize is too small |
| Long Text: | File size specified for resize datafile/temporary file causes bitmap control structures to overlap. |
| Repair Text: | From Oracle doc: Increase the specification for the file size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tablespace/Segment Verification cannot proceed |
| Long Text: | Corruption was detected during verification which cannot be dealt with |
| Repair Text: | From Oracle doc: Do manual verification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for alter of TEMPORARY TABLESPACE |
| Long Text: | Invalid option for alter of temporary tablespace was specified. |
| Repair Text: | From Oracle doc: Specify one of the valid options: ADD TEMPFILE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for CREATE/ALTER TABLESPACE |
| Long Text: | Invalid option for create/alter tablespace of type locally-managed. |
| Repair Text: | From Oracle doc: Specify one of the valid options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Applies to locally-managed tablespaces only. Tablespace '%s' is not locally-managed |
| Long Text: | Operation which is only applicable to locally-managed tablespaces is specified for a dictionary-managed tablespace. |
| Repair Text: | From Oracle doc: Reissue operation for a different tablespace, or do not issue it at all, since it does not apply for the given tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3220 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBMS_ADMIN_PACKAGE required parameter is NULL or missing |
| Long Text: | Some of the procedures was called with missing or NULL parameters. |
| Repair Text: | From Oracle doc: Specify the missing parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | segment only contains %s blocks of unused space above high water mark |
| Long Text: | Attempt to preserve too many blocks. |
| Repair Text: | From Oracle doc: Reduce the KEEP amount. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the INITIAL extent may not be deallocated |
| Long Text: | Attempt to deallocate space from the segment which was truncated prior to the 7.3 release. |
| Repair Text: | From Oracle doc: Increase the KEEP amount, or truncate the segment, and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to allocate an extent of %s blocks from tablespace %s |
| Long Text: | An attempt was made to specify a HASH_MULTIBLOCK_IO_COUNT value that is greater than the tablespace's NEXT value. |
| Repair Text: | From Oracle doc: Increase the value of NEXT for the tablespace using ALTER TABLESPACE DEFAULT STORAGE or decrease the value of HASH_MULTIBLOCK_IO_COUNT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend table %s.%s subpartition %s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for table subpartition segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend index %s.%s subpartition %s by %s in tablespace %s |
| Long Text: | Failed to allocate an extent for index subpartition segment in tablespace. |
| Repair Text: | From Oracle doc: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in table %s.%s subpartition %s |
| Long Text: | A table subpartition tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If the value of MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3236 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max # extents (%s) reached in index %s.%s subpartition %s |
| Long Text: | An index subpartition tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If the value of MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3237 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Initial Extent of specified size cannot be allocated |
| Long Text: | Too large a size for an initial extent due to freelist group specification. |
| Repair Text: | From Oracle doc: Reduce number of freelist groups specified for the segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3238 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to extend LOB segment %s.%s subpartition %s by %s in tablespace %s |
| Long Text: | An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated. |
| Repair Text: | From Oracle doc: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3239 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maxextents (%s) reached in LOB segment %s.%s subpartition %s |
| Long Text: | A LOB subpartition segment tried to extend past MAXEXTENTS. |
| Repair Text: | From Oracle doc: If the value of MAXEXTENTS is less than the system maximum, raise it. Otherwise, re-create the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3274 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified |
| Long Text: | The DEALLOCATE option and the ALLOCATE option are specified in the same command. |
| Repair Text: | From Oracle doc: Choose one of the options or issue two separate commands. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3275 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate DEALLOCATE option specification |
| Long Text: | The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once. |
| Repair Text: | From Oracle doc: Specify the option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate ALLOCATE EXTENT option specification |
| Long Text: | The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once. |
| Repair Text: | From Oracle doc: Specify the option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SIZE specified |
| Long Text: | The specified value must be an integer. |
| Repair Text: | From Oracle doc: Choose an appropriate integer value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate ALLOCATE EXTENT option specification |
| Long Text: | An option (DATAFILE, SIZE or INSTANCE) was specified more than once. |
| Repair Text: | From Oracle doc: Specify each option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3279 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid INSTANCE specified |
| Long Text: | The specified value is not recognized as a valid instance name. |
| Repair Text: | From Oracle doc: Use a valid name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3280 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid DATAFILE filename specified |
| Long Text: | A character string literal is expected, but not found. |
| Repair Text: | From Oracle doc: Specify file names using character string literals. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALLOCATE EXTENT option |
| Long Text: | An option other than DATAFILE, SIZE or INSTANCE was specified. |
| Repair Text: | From Oracle doc: Remove invalid option and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3282 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing ALLOCATE EXTENT option |
| Long Text: | No ALLOCATE EXTENT options were specified. |
| Repair Text: | From Oracle doc: Specified one or more of the following options: DATAFILE, SIZE or INSTANCE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3283 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified datafile %s does not exist |
| Long Text: | The datafile does not exist. |
| Repair Text: | From Oracle doc: Retry the option with the correct datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3284 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s is not a member of tablespace %s |
| Long Text: | The specified datafile does not belong to the tablespace that the object resides in. |
| Repair Text: | From Oracle doc: Retry the option with the correct datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3286 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALLOCATE EXTENT not valid for HASH CLUSTERS |
| Long Text: | The cluster cannot use the allocate extent option because it is a hash cluster. |
| Repair Text: | From Oracle doc: Do not use this command on a hash cluster. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3287 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid FREELIST GROUP specified |
| Long Text: | The specified FREELIST GROUP number is invalid. |
| Repair Text: | From Oracle doc: Choose a number between 1 and the number of freelist groups for this object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3288 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | both FREELIST GROUP and INSTANCE parameters may not be specified |
| Long Text: | Both FREELIST GROUP and INSTANCE were specified in clause. |
| Repair Text: | From Oracle doc: Remove one of the two parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid truncate command - missing CLUSTER or TABLE keyword |
| Long Text: | Invalid object specification given. |
| Repair Text: | From Oracle doc: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3291 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid truncate option - missing STORAGE keyword |
| Long Text: | Expected STORAGE keyword. |
| Repair Text: | From Oracle doc: Either specify DROP STORAGE or REUSE STORAGE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3292 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Table to be truncated is part of a cluster |
| Long Text: | The table being truncated is a member of a cluster. |
| Repair Text: | From Oracle doc: Either use TRUNCATE CLUSTER or DROP TABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3293 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cluster to be truncated is a HASH CLUSTER |
| Long Text: | Only INDEX CLUSTERS can be truncated. |
| Repair Text: | From Oracle doc: Drop and re-create the HASH CLUSTER instead of using truncate. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3296 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot resize datafile - file %s not found |
| Long Text: | The specified datafile is not available for resizing. |
| Repair Text: | From Oracle doc: Ensure that the datafile name is valid, and if so, ensure the file is accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3297 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file contains used data beyond requested RESIZE value |
| Long Text: | Some portion of the file in the region to be trimmed is currently in use by a database object. |
| Repair Text: | From Oracle doc: Drop or move segments containing extents in this region prior to resizing the file, or choose a resize value such that only free space is in the trimmed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3298 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot shrink datafile - file %s is under hot backup |
| Long Text: | Attempt to shrink a datafile while it is under hot backup. This is not allowed. |
| Repair Text: | From Oracle doc: Retry shrinking the file after the hot backup completes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-3299 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create dictionary table %s |
| Long Text: | A dictionary table is created upon the first execution of the command ALTER DATABASE DATAFILE AUTOEXTEND ON for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace. |
| Repair Text: | From Oracle doc: See action for next error message in error stack. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the sum of PCTUSED and PCTFREE cannot exceed 100 |
| Long Text: | The sum of PCTUSED and PCTFREE for a cluster or table exceeds 100. |
| Repair Text: | From Oracle doc: Create the table/cluster specifying values whose sum is less than or equal to 100. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence parameter %s must be an integer |
| Long Text: | string (a sequence parameter) specified was not an integer. |
| Repair Text: | From Oracle doc: Create the sequence, giving the specified parameter an integer value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | INCREMENT must be a non-zero integer |
| Long Text: | A sequence increment was specified to be zero. |
| Repair Text: | From Oracle doc: Specify the increment to be a non-zero value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence parameter %s exceeds maximum size allowed (%s digits) |
| Long Text: | string (a sequencer parameter) had too many digits. |
| Repair Text: | From Oracle doc: Specify the parameter with the allowed number of digits. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MINVALUE must be less than MAXVALUE |
| Long Text: | MINVALUE was specified to be greater than or equal to MAXVALUE. |
| Repair Text: | From Oracle doc: Specify a MINVALUE that is less than MAXVALUE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | INCREMENT must be less than MAXVALUE minus MINVALUE |
| Long Text: | The INCREMENT specified is greater than or equal to MAXVALUE-MINVALUE. |
| Repair Text: | From Oracle doc: Specify an INCREMENT that is less than MAXVALUE-MINVALUE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | START WITH cannot be less than MINVALUE |
| Long Text: | The given starting value is less than MINVALUE. |
| Repair Text: | From Oracle doc: Make sure that the starting value is greater than or equal to MINVALUE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MINVALUE cannot be made to exceed the current value |
| Long Text: | The given MINVALUE would be greater than the current value. |
| Repair Text: | From Oracle doc: Always make sure that MINVALUE is less than or equal to the current value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | START WITH cannot be more than MAXVALUE |
| Long Text: | The starting value would be larger than MAXVALUE. |
| Repair Text: | From Oracle doc: Make sure that the starting value is less than MAXVALUE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXVALUE cannot be made to be less than the current value |
| Long Text: | The current value exceeds the given MAXVALUE. |
| Repair Text: | From Oracle doc: Make sure that the new MAXVALUE is larger than the current value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the number of values to CACHE must be greater than 1 |
| Long Text: | The value in the CACHE clause was one. |
| Repair Text: | From Oracle doc: Specify NOCACHE, or a value larger than one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence %s must range between %s and %s |
| Long Text: | The value specified for one of the sequence parameters exceeds limits. |
| Repair Text: | From Oracle doc: Specify a parameter within these limits. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object is not a sequence |
| Long Text: | The object specified cannot have sequence DDLs performed on it. |
| Repair Text: | From Oracle doc: Re-enter the statement being careful with the spelling of the name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number to CACHE must be less than one cycle |
| Long Text: | The number to CACHE specified in a CREATE SEQUENCE statement exceeds the number of values in a cycle. |
| Repair Text: | From Oracle doc: Enlarge the cycle or cache fewer values, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | descending sequences that CYCLE must specify MINVALUE |
| Long Text: | A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again. |
| Repair Text: | From Oracle doc: Re-create the sequence, specifying the value at which it is to begin. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ascending sequences that CYCLE must specify MAXVALUE |
| Long Text: | A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again. |
| Repair Text: | From Oracle doc: Recreate the sequence, specifying the value at which it is to begin. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence %s no longer exists |
| Long Text: | Sequence was dropped while processing its next value. |
| Repair Text: | From Oracle doc: Re-create the sequence. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s (length = %s) for parameter max_dump_file_size |
| Long Text: | Neither did the string supplied for MAX_DUMP_FILE_SIZE parameter match the "UNLIMITED" string value nor did it represent a base 10 integer. |
| Repair Text: | From Oracle doc: Reassign a proper value to this parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s for parameter _scn_scheme |
| Long Text: | The value specified for initialization parameter _SCN_SCHEME is not recognized as one of the defined schemes. |
| Repair Text: | From Oracle doc: Reassign a proper value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SCN scheme incompatible with other instances |
| Long Text: | Either different instances are running incompatible Oracle releases or different values have been assigned to the _SCN_SCHEME initialization parameter on different instances. |
| Repair Text: | From Oracle doc: Make sure the _SCN_SCHEME initialization parameter is set to the same value on all instances. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | deadlock detected while trying to lock object stringstringstringstring%s |
| Long Text: | While trying to lock a library object, a deadlock is detected. |
| Repair Text: | From Oracle doc: Retry the operation later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | timeout occurred while waiting to lock object stringstringstringstring%s |
| Long Text: | While waiting to lock a library object, a timeout is occurred. |
| Repair Text: | From Oracle doc: Retry the operation later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | nowait requested, but had to wait to lock dictionary object |
| Long Text: | Had to wait to lock a library object during a nowait request. |
| Repair Text: | From Oracle doc: Retry the operation later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot generate diana for object stringstringstringstring%s |
| Long Text: | Cannot generate diana for an object because of lock conflict. |
| Repair Text: | From Oracle doc: Report this error to your support representative. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error ORA-%s occurred when querying stringstring%s |
| Long Text: | The table or view being queried might be missing. The error number indicates the error. |
| Repair Text: | From Oracle doc: Fix the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | out of process memory when trying to allocate %s bytes (%s,%s) |
| Long Text: | Operating system process private memory has been exhausted. |
| Repair Text: | From Oracle doc: See the database administrator or operating system administrator to increase process memory quota. There may be a bug in the application that causes excessive allocations of process memory space. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to allocate %s bytes of shared memory ("%s","%s","%s","%s") |
| Long Text: | More shared memory is needed than was allocated in the shared pool. |
| Repair Text: | From Oracle doc: If the shared pool is out of memory, either use the DBMS_SHARED_POOL package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | package specification must be created first before creating package body |
| Long Text: | Attempt to create a package body before creating its package specification. |
| Repair Text: | From Oracle doc: Create the package specification first before creating the package body. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | procedure, function, package, or package body does not exist |
| Long Text: | Attempt to access a procedure, function, package, or package body that does not exist. |
| Repair Text: | From Oracle doc: Make sure the name is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s does not exist |
| Long Text: | An object name was specified that was not recognized by the system. Following are possible causes: An invalid name for a table, view, sequence, procedure, function, package, or package body was entered. Since the system could not recognize the invalid name, it responded with the message that the named object does not exist. An attempt was made to rename an index or a cluster, or some other object that cannot be renamed. |
| Repair Text: | From Oracle doc: Check the spelling of the named object and rerun the code. (Valid names of tables, views, functions, etc. can be listed by querying the data dictionary.) |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | procedure, function, package, or type is not allowed here |
| Long Text: | A procedure, function, or package was specified in an inappropriate place in a statement. |
| Repair Text: | From Oracle doc: Make sure the name is correct or remove it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | errors during recompilation/revalidation of %s.%s |
| Long Text: | This message indicates the object to which the following errors apply. The errors occurred during implicit recompilation/revalidation of the object. |
| Repair Text: | From Oracle doc: Check the following errors for more information, and make the necessary corrections to the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4046 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | results of compilation are too large to support |
| Long Text: | Attempt to compile and store a large stored procedure that results in compilation data that is too large for the system to support or store. |
| Repair Text: | From Oracle doc: Reduce the size of the store procedure by splitting it into smaller stored procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4047 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object specified is incompatible with the flag specified |
| Long Text: | The object type implied by the flag does not match the type of object specified. |
| Repair Text: | From Oracle doc: Specify the correct object, or use the appropriate flag. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4050 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or missing procedure, function, or package name |
| Long Text: | The required procedure, function, or package name is invalid or missing. |
| Repair Text: | From Oracle doc: Specify a valid name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4051 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user %s cannot use database link %s.%s |
| Long Text: | During forwarding of a remote object access, an attempt was made to use a non-existent database link or one owned by a user other than the logon user or PUBLIC. |
| Repair Text: | From Oracle doc: Change your database link structure so that all indirect remote accesses are done from the same userid that originates the request. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred when looking up remote object stringstringstringstring%s |
| Long Text: | An error has occurred when trying to look up a remote object. |
| Repair Text: | From Oracle doc: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred when validating remote object stringstringstringstring%s |
| Long Text: | An error has occurred when trying to validate a remote object. |
| Repair Text: | From Oracle doc: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link %s does not exist |
| Long Text: | During compilation of a PL/SQL block, an attempt was made to use a non-existent database link. |
| Repair Text: | From Oracle doc: Either use a different database link or create the database link. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4055 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Aborted: "%s" formed a non-REF mutually-dependent cycle with "%s". |
| Long Text: | This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2); |
| Repair Text: | From Oracle doc: Break the cycle (possibly by adding a REF or by using another type). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to execute %s |
| Long Text: | Attempt to execute a stored procedure without sufficient privileges. |
| Repair Text: | From Oracle doc: Get necessary privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | existing state of %s has been invalidated |
| Long Text: | Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped. |
| Repair Text: | From Oracle doc: Try again; this error should have caused the existing state of all packages to be re-initialized. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4062 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s of %s has been changed |
| Long Text: | Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp or signature that is different from the current timestamp/signature of the procedure. |
| Repair Text: | From Oracle doc: Recompile the caller in order to pick up the new timestamp. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4063 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s has errors |
| Long Text: | Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types. |
| Repair Text: | From Oracle doc: Fix the errors and/or create referenced objects as necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4064 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not executed, invalidated %s |
| Long Text: | Attempt to execute a stored procedure that has been invalidated. |
| Repair Text: | From Oracle doc: Recompile the stored procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4065 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not executed, altered or dropped %s |
| Long Text: | Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure. |
| Repair Text: | From Oracle doc: Recompile its dependents. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4066 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-executable object, %s |
| Long Text: | Attempt to execute a non-procedure. |
| Repair Text: | From Oracle doc: Make sure that a correct name is given. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4067 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not executed, %s does not exist |
| Long Text: | Attempt to execute a non-existent stored procedure. |
| Repair Text: | From Oracle doc: Make sure that a correct name is given. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4068 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | existing state of packagesstringstring%s has been discarded |
| Long Text: | An error occurred when attempting to execute a stored procedure. |
| Repair Text: | From Oracle doc: Refer to the accompanying messages and fix the error mentioned. Try the procedure again after proper reinitialization of any application's state. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4070 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid trigger name |
| Long Text: | An invalid trigger name was specified. |
| Repair Text: | From Oracle doc: Verify that trigger name is not a reserved keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing BEFORE, AFTER or INSTEAD OF keyword |
| Long Text: | The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause. |
| Repair Text: | From Oracle doc: Specify either BEFORE, AFTER or INSTEAD OF. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4072 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid trigger type |
| Long Text: | An invalid trigger type was given. |
| Repair Text: | From Oracle doc: Specify either INSERT, UPDATE or DELETE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4073 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column list not valid for this trigger type |
| Long Text: | A column list was specified for a non-update trigger type. |
| Repair Text: | From Oracle doc: Remove the column list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid REFERENCING name |
| Long Text: | An invalid name was given in the referencing clause. |
| Repair Text: | From Oracle doc: Verify the referencing name is not a reserved word. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4075 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid trigger action |
| Long Text: | An statement was given for the trigger action. |
| Repair Text: | From Oracle doc: Re-specify the trigger action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4076 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid NEW or OLD specification |
| Long Text: | An invalid NEW or OLD specification was given for a column. |
| Repair Text: | From Oracle doc: Re-specify the column using the correct NEW or OLD specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4077 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | WHEN clause cannot be used with table level triggers |
| Long Text: | The when clause can only be specified for row level triggers. |
| Repair Text: | From Oracle doc: Remove the when clause or specify for each row. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OLD and NEW values cannot be identical |
| Long Text: | The referencing clause specifies identical values for NEW and OLD. |
| Repair Text: | From Oracle doc: Re-specify either the OLD or NEW referencing value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4079 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid trigger specification |
| Long Text: | The create TRIGGER statement is invalid. |
| Repair Text: | From Oracle doc: Check the statement for correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4080 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trigger '%s' does not exist |
| Long Text: | The TRIGGER name is invalid. |
| Repair Text: | From Oracle doc: Check the trigger name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4081 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trigger '%s' already exists |
| Long Text: | The TRIGGER name or type already exists. |
| Repair Text: | From Oracle doc: Use a different trigger name or drop the trigger which is of the same name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NEW or OLD references not allowed in table level triggers |
| Long Text: | The trigger is accessing "new" or "old" values in a table trigger. |
| Repair Text: | From Oracle doc: Remove any new or old references. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4083 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid trigger variable '%s' |
| Long Text: | The variable referenced in the trigger body is invalid. |
| Repair Text: | From Oracle doc: See Oracle8i SQL Reference for valid trigger variable types. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change NEW values for this trigger type |
| Long Text: | New trigger variables can only be changed in before row insert or update triggers. |
| Repair Text: | From Oracle doc: Change the trigger type or remove the variable reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4085 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change the value of an OLD reference variable |
| Long Text: | Old values can only be read and not changed. |
| Repair Text: | From Oracle doc: Do not attempt to change an old variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4086 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trigger description too long, move comments into triggering code |
| Long Text: | The trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the "when" clause or the text of the PL/SQL code executed for the trigger. |
| Repair Text: | From Oracle doc: If the trigger description contains a large comment, move that comment into the PL/SQL code for the trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4087 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change the value of ROWID reference variable |
| Long Text: | ROWIDs can only be read and not changed. |
| Repair Text: | From Oracle doc: Do not attempt to change an ROWID value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4088 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error during execution of trigger '%s.%s' |
| Long Text: | A runtime error occurred during execution of a trigger. |
| Repair Text: | From Oracle doc: Check the triggers which were involved in the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4089 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create triggers on objects owned by SYS |
| Long Text: | An attempt was made to create a trigger on an object owned by SYS. |
| Repair Text: | From Oracle doc: Do not create triggers on objects owned by SYS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4090 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s' specifies same table, event and trigger time as '%s' |
| Long Text: | Trigger is of duplicate event and trigger time. |
| Repair Text: | From Oracle doc: Combine the triggering information into one trigger which is fired at the given time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4091 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table %s.%s is mutating, trigger/function may not see it |
| Long Text: | A trigger (or a user defined PL/SQL function that is referenced in this statement) attempted to look at (or modify) a table that was in the middle of being modified by the statement which fired it. |
| Repair Text: | From Oracle doc: Rewrite the trigger (or function) so it does not read that table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4092 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot %s in a trigger |
| Long Text: | A trigger attempted to commit or roll back. |
| Repair Text: | From Oracle doc: Rewrite the trigger so it does not commit or roll back. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4093 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | references to columns of type LONG are not allowed in triggers |
| Long Text: | A trigger attempted to reference a long column in the triggering table. |
| Repair Text: | From Oracle doc: Do not reference the long column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4094 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table %s.%s is constraining, trigger may not modify it |
| Long Text: | A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement. |
| Repair Text: | From Oracle doc: Rewrite the trigger so that it does not modify that table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4095 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trigger '%s' already exists on another table, cannot replace it |
| Long Text: | Cannot replace a trigger which already exists on a different table than the one being replaced. |
| Repair Text: | From Oracle doc: Drop the trigger with the same name and re-create it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4096 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trigger '%s' has a WHEN clause which is too large, limit 2K |
| Long Text: | A trigger's WHEN clause is limited to 2K for dictionary storage reasons. The trigger being created exceeded that size. |
| Repair Text: | From Oracle doc: Use a smaller WHEN clause. Note, the trigger body could be used to perform the same limiting action as the WHEN clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4097 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DDL conflict while trying to drop or alter a trigger |
| Long Text: | An attempt was made to concurrently perform two DDL operations on a trigger or trigger table. |
| Repair Text: | From Oracle doc: Investigate the new state of the trigger and retry the DDL operation, if still appropriate. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4098 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trigger '%s.%s' is invalid and failed re-validation |
| Long Text: | A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger. |
| Repair Text: | From Oracle doc: Options are to resolve the compilation/authorization errors, disable the trigger, or drop the trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4099 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trigger '%s' is valid but not stored in compiled form |
| Long Text: | A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release. |
| Repair Text: | From Oracle doc: Alter compile the trigger to create the trigger in stored form. Also, you may want to review that a proper upgrade was done. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4930 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | open sequence number failed or initial state is valid |
| Long Text: | Either Shared Sequence Number operating system component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly. |
| Repair Text: | From Oracle doc: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the operating system command ps -ef|grep instance_name. Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by issuing the ipcs -b operating system command. If there are shared memory segments or processes still on the system, use SVRMGRL to shut down the instance with the abort option. If the instance is not up, verify that the cluster software and/or the hardware is installed and working. Log in as superuser and issue the CNXSHOW command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital's customer support organization. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4931 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to set initial sequence number value |
| Long Text: | A call to the SSN failed to set the sequence number to its initial value, possibly caused by an MC hardware problem. |
| Repair Text: | From Oracle doc: Verify that the MC hardware is functioning properly. If it is not, contact Digital's customer support organization. If it is, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4932 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | increment or adjust of sequence number failed |
| Long Text: | A call to the SSN failed to increment the sequence number. |
| Repair Text: | From Oracle doc: Verify that the MC hardware is functioning properly. If it is not, contact Digital's customer support organization. If it is, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4933 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | initial service identifier is non-zero |
| Long Text: | A valid service identifier existed before the sequence number service was opened. |
| Repair Text: | From Oracle doc: Verify that the instance is completely shut down. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4934 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to obtain the current sequence number |
| Long Text: | A call to the SSN failed to return its current value. Either there are many errors occurring on the MC hardware, or the sequence number has become invalid and cannot be validated. |
| Repair Text: | From Oracle doc: Verify that the MC hardware is functioning properly. If it is, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-4935 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to get/convert SCN recovery lock |
| Long Text: | A process has timed out trying to get or convert the SCN recovery lock. Another process probably has the lock in EX or SHR mode, but is not releasing it. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: port open failure |
| Long Text: | Autologin unable to open port. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: port set-up failure |
| Long Text: | Autologin unable to change port attributes. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: port read failure |
| Long Text: | Autologin unable to read from port. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: port write failure |
| Long Text: | Autologin unable to write to port. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: dialogue file open failure |
| Long Text: | Autologin unable to open dialogue file. |
| Repair Text: | From Oracle doc: Check connect string for accuracy/typos. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: dialogue file read failure |
| Long Text: | Autologin unable to read dialogue file. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: dialogue execute failure |
| Long Text: | Expected response never received. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: bad dialogue format |
| Long Text: | Dialogue file contains syntax error. |
| Repair Text: | From Oracle doc: Correct the dialogue file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: dialogue filename too long |
| Long Text: | Full file specification for dialogue file exceeds 64 bytes. |
| Repair Text: | From Oracle doc: Amend connect string accordingly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: dialogue file too long |
| Long Text: | Dialogue file exceeds 768 bytes in length. |
| Repair Text: | From Oracle doc: Simplify dialogue (e.g. remove comments, redundant white space), or split into two and link with the MORE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: dialogue too long |
| Long Text: | One of the following: Dialogue contains more than 24 exchange blocks Dialogue send string exceeds 84 bytes in length |
| Repair Text: | From Oracle doc: Simplify dialogue or split into two and link with the MORE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: message receive failure |
| Long Text: | Asynchronous driver gets I/O error while doing network read operation. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: message send failure |
| Long Text: | Asynchronous driver gets I/O error while doing network write operation. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: invalid login (connect) %s |
| Long Text: | Syntax error in login string. |
| Repair Text: | From Oracle doc: Resubmit with correct string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: initialisation failure |
| Long Text: | Asynchronous driver unable to complete initialization. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: connect failed |
| Long Text: | Asynchronous driver unable to establish connection with partner. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: channel open failure |
| Long Text: | No free channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: port open failure |
| Long Text: | Asynchronous driver unable to open port. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: VTM error |
| Long Text: | Virtual Terminal Manager unable to read/write to port. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: Configuration error |
| Long Text: | Asynchronous driver generated for server-only, but client service requested. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: port close failure |
| Long Text: | Asynchronous driver unable to close port. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: channel close failure |
| Long Text: | Asynchronous driver unable to close channel. |
| Repair Text: | From Oracle doc: Check log file for operating system-specific error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: unable to intialise for logging |
| Long Text: | Asynchronous driver unable to initialize for logging I/O. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETASY: port assignment failure |
| Long Text: | Asynchronous driver unable to assign port to channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, unrecognized node name |
| Long Text: | Node name specified in host string is unknown (probably misspelled). |
| Repair Text: | From Oracle doc: Retry with correct node name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, unrecognized object name |
| Long Text: | Host string contains reference to object (which does not exist): @d:node-obj => object is ORDNobj;
when node is UNIX, the object is ORDNobj @d:node::"task=obj" => object is obj; when node is VMS, the object is obj.COM when node is UNIX, the object is obj |
| Repair Text: | From Oracle doc: Retry with correct object name or create the required object on host node. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, access control data rejected |
| Long Text: | Host string contains invalid username/password. |
| Repair Text: | From Oracle doc: Retry with correct username/password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6033 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, partner rejected connection |
| Long Text: | Connection with partner was made but was rejected. |
| Repair Text: | From Oracle doc: Contact your network administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6034 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, partner exited unexpectedly |
| Long Text: | Connection with host node was made but partner aborted. |
| Repair Text: | From Oracle doc: Make sure object (see 06031, above) is working (for VMS run the command file and make sure that the Oracle server process starts up); sometimes happens when the network/node is under stress; in this case, a retry often works. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, insufficient resources |
| Long Text: | Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use. |
| Repair Text: | From Oracle doc: Contact your network administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, node unreachable |
| Long Text: | Host node is down. |
| Repair Text: | From Oracle doc: Contact your network administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed |
| Long Text: | Connect failed for unexpected reason (see OSD error). |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: invalid login (connect) %s |
| Long Text: | Syntax error in login string. |
| Repair Text: | From Oracle doc: Resubmit with correct string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: disconnect failed |
| Long Text: | Driver gets error while doing network close operation. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: message receive failure |
| Long Text: | Driver gets I/O error while doing network read operation. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: message send failure |
| Long Text: | Driver gets I/O error while doing network write operation. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETDNT: connect failed, byte count quota exceeded |
| Long Text: | Connect failed because of insufficient byte count quota. |
| Repair Text: | From Oracle doc: Increase byte count quota. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: cannot allocate context area |
| Long Text: | Insufficient dynamic memory available for connection context area. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: remote host is unknown |
| Long Text: | Host name specified in the login (connect) string is unknown. |
| Repair Text: | From Oracle doc: Check spelling; make sure name is in the TCP/IP HOST file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: socket creation failure |
| Long Text: | Process open file quota probably exceeded. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: ORACLE network server not found |
| Long Text: | No entry in SERVICES file for Oracle server. |
| Repair Text: | From Oracle doc: Add (ORASRV) entry to the TCP/IP SERVICES file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: connect to host failed |
| Long Text: | Connection attempt to remote host has failed. Probably means that the SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up (check the latter by targeting it with Telnet). |
| Repair Text: | From Oracle doc: Start the SQL*Net TCP/IP server process on the remote host. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: message receive failure |
| Long Text: | I/O error occurred while attempting network read operation. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: message send failure |
| Long Text: | I/O error occurred while attempting network write operation. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: disconnect failure |
| Long Text: | Error occurred while closing a socket. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: invalid buffer size |
| Long Text: | The buffer size specified in the login string exceeds the allowed maximum (of 4096). |
| Repair Text: | From Oracle doc: Re-submit with valid buffer size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: Too many connections |
| Long Text: | The maximum no. of concurrently open connections has been reached. |
| Repair Text: | From Oracle doc: Exit an application with an open connection which is no longer required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: SID lookup failure |
| Long Text: | From the remote host's SQL*Net TCP/IP server: the database SID, specified in the login (connect) string, was not recognized. |
| Repair Text: | From Oracle doc: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net TCP/IP server). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to create ORACLE logicals |
| Long Text: | The host's SQL*Net TCP/IP server was unable to create the necessary logical names required by the Oracle server process. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to create ORASRV process |
| Long Text: | The host's SQL*Net TCP/IP server was unable to create the Oracle server process. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6117 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to create ORASRV: quota exceeded |
| Long Text: | The host's SQL*Net TCP/IP server was unable to create the Oracle server process because of quota depletion. |
| Repair Text: | From Oracle doc: Increase quota allocations to the SQL*Net TCP/IP server process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6118 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to complete handshake with ORASRV |
| Long Text: | The Oracle server process was started but failed to complete its initialization. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6119 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: spurious client request |
| Long Text: | The host's SQL*Net TCP/IP server was unable to recognize this connection request. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: network driver not loaded |
| Long Text: | The TCP/IP network driver is not loaded. |
| Repair Text: | From Oracle doc: Check that the TCP/IP driver is loaded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: access failure |
| Long Text: | The host's SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: setup failure |
| Long Text: | The host's SQL*Net TCP/IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: cannot set KEEPALIVE |
| Long Text: | The host's SQL*Net TCP/IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: timeout waiting for ORASRV |
| Long Text: | The Oracle server process was started but failed to respond after N seconds. |
| Repair Text: | From Oracle doc: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = no_of_secs which will come into effect the next time the SQL*Net TCP/IP server is started. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: ORASRV exited unexpectedly |
| Long Text: | The Oracle server process was started but exited unexpectedly. Possible causes: Insufficient quotas to run ORASRV Oracle is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_SRVTnn_sid.OUT |
| Repair Text: | From Oracle doc: If appropriate action is not obvious from the ORASRV output file, then contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: ORASRV unable to open network connection |
| Long Text: | The Oracle server process was started but was unable to open the socket passed to it by TCPSRV. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to change username |
| Long Text: | The host's SQL*Net TCP/IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host operating system). |
| Repair Text: | From Oracle doc: Create new user account on host. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to create mailbox |
| Long Text: | The host's SQL*Net TCP/IP server was unable to create a mailbox (needed for IPC communication with the Oracle server process). See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6129 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to transfer socket ownership to ORASRV |
| Long Text: | The host's SQL*Net TCP/IP server was unable to transfer the network communication handle to the Oracle server process. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6130 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: host access denied |
| Long Text: | The host's SQL*Net TCP/IP server rejected this connection request because the client node does not have access privilege - as determined by the contents of the Valid Node Table (VNT), a component of the host's CONFIG.ORA. |
| Repair Text: | From Oracle doc: To grant access, add appropriate entry to the host's VNT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6131 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: user access denied |
| Long Text: | The host's SQL*Net TCP/IP server rejected this connection request because the client user(name) does not have access privilege, as determined by the contents of the Username Mapping Table (UMT), a component of the host's CONFIG.ORA. |
| Repair Text: | From Oracle doc: To grant access, add appropriate entry to the host's UMT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6132 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: access denied, wrong password |
| Long Text: | The host SQL*Net TCP/IP server rejected this connection request because the client password did not match the host password. |
| Repair Text: | From Oracle doc: To grant access, get passwords in sync. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6133 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: file not found |
| Long Text: | The host's SQL*Net TCP/IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request. |
| Repair Text: | From Oracle doc: Check CONFIG.ORA for spelling; make correct entry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6134 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: file access privilege violation |
| Long Text: | The host's SQL*Net TCP/IP server did not have READ/ EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request. |
| Repair Text: | From Oracle doc: Change protection on SID mapping file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6135 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: connection rejected; server is stopping |
| Long Text: | The host's SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping. |
| Repair Text: | From Oracle doc: Restart SQL*Net TCP/IP server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6136 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: error during connection handshake |
| Long Text: | Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6137 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: error during connection handshake |
| Long Text: | Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6138 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: error during connection handshake |
| Long Text: | Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6140 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: no such user |
| Long Text: | A proxy login connect attempt failed because the client username has no counterpart on the host. |
| Repair Text: | From Oracle doc: Try again with a user that has a counterpart on the host. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6141 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: no privilege for user |
| Long Text: | A proxy login connect attempt failed because the SQL*Net TCP/IP server had insufficient privileges to access the proxy account. |
| Repair Text: | From Oracle doc: Change account protection; change server privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6142 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: error getting user information |
| Long Text: | A proxy login connect attempt failed because the SQL*Net TCP/IP server was unable to access the proxy account. See the SQL*Net TCP/IP server log file for more details. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6143 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | NETTCP: maximum connections exceeded |
| Long Text: | The connect failed because the maximum concurrent connections supported by the host's SQL*Net TCP/IP server has already been reached. |
| Repair Text: | From Oracle doc: Wait for a short period and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6144 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | NETTCP: SID (database) is unavailable |
| Long Text: | The database administrator on the host has varied the SID offline. |
| Repair Text: | From Oracle doc: Wait for it to be varied back online. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6145 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETTCP: unable to start ORASRV: images not installed |
| Long Text: | The host's SQL*Net TCP/IP server was unable to start the Oracle server process because the Oracle protected images were not installed. |
| Repair Text: | From Oracle doc: Install the images. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, can't create mailbox |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, can't attach to mailbox |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, can't spawn ORASRV process |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, handshake failure |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, can't access ORASRV2.COM |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, can't create logical name |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: message receive failure |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: message send failure |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: invalid login (connect) %s |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, mailbox already exists |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, ORASRV exited unexpectedly |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, timeout waiting for ORASRV |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, logical name table is full |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, insufficient quotas to create ORASRV |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, ORASRV protected image not installed |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TWOTASK: connect failed, can't find ORASRV image file |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot allocate send and receive buffers |
| Long Text: | Two-task driver could not allocate data buffers. |
| Repair Text: | From Oracle doc: There is insufficient memory to run your program. Kill off other processes to free up memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot translate address file name |
| Long Text: | ORACLE_HOME environment variable not set. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME environment variable has been properly set and exported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6252 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot open address file |
| Long Text: | The NTT two-task driver could not open a file containing address information. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6253 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot read arguments from address file |
| Long Text: | The NTT two-task driver could not read addressing information from its addressing file. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6254 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot share connection to cube |
| Long Text: | The NTT two-task driver could not share a connection to the cube. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6255 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot read pid of remote process |
| Long Text: | An error occurred while reading the NTT communications link. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6256 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: remote fork failed |
| Long Text: | The Oracle listener process on the cube could not fork off a shadow process. |
| Repair Text: | From Oracle doc: The instance you are trying to connect to probably does not have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6257 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot send command line to shadow process |
| Long Text: | An error occurred while writing the NTT communications link. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6258 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot allocate context area |
| Long Text: | Two-task driver could not allocate data buffers. |
| Repair Text: | From Oracle doc: There is insufficient memory to run your program. Kill off other processes to free up memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6259 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot read from remote process |
| Long Text: | An error occurred while reading the NTT communications link. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot write to remote process |
| Long Text: | An error occurred while writing the NTT communications link. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: nrange() failed |
| Long Text: | The call to NRANGE() failed while attempting to establish a connection. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: nfconn() failed |
| Long Text: | The call to NFCONN() failed while attempting to establish a connection. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: out of memory in pi_connect |
| Long Text: | Two-task driver could not allocate data buffers. |
| Repair Text: | From Oracle doc: There is insufficient memory to run your program. Kill off other processes to free up memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6264 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: data protocol error |
| Long Text: | The NTT two-task driver received an unexpected message type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: break protocol error |
| Long Text: | The NTT two-task driver received an unexpected message type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: bad write length |
| Long Text: | The NTT two-task driver failed on an internal consistency check. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6267 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: bad state |
| Long Text: | The NTT two-task driver failed on an internal consistency check. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6268 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETNTT: cannot read /etc/oratab |
| Long Text: | The NTT two-task driver could not read configuration information from /etc/oratab. |
| Repair Text: | From Oracle doc: Make sure /etc/oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6300 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IPA: Disconnect failure |
| Long Text: | A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues. |
| Repair Text: | From Oracle doc: If there is no message queue, restart the SQL*Net IPA servers using IPACTL. Otherwise contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Cannot allocate driver context |
| Long Text: | The memory pool is exhausted. |
| Repair Text: | From Oracle doc: Check the circumstances and try to allocate less memory in your program or adjust the parameters in your INIT.ORA file and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Cannot connect to remote host |
| Long Text: | One of the following: There is no ADI server defined to reflect a connection to the specified host. The remote host is not known by the local system. The Oracle kernel on the remote host is not generated with the IPA driver |
| Repair Text: | From Oracle doc: Check sequentially for the above causes and eliminate the actual cause found. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Message send error |
| Long Text: | The SQL*Net IPA driver could not write the message into the message queue. |
| Repair Text: | From Oracle doc: Make sure that the message queue exists and is accessible. If necessary rerun IPACTL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Message receive error |
| Long Text: | The SQL*Net IPA driver could not read a message from the message queue. |
| Repair Text: | From Oracle doc: Make sure that the message queue exists and is accessible. If necessary rerun IPACTL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Illegal message type |
| Long Text: | The communication between user and Oracle is out of synchronization. This message should not normally be issued. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Message write length error |
| Long Text: | The IPA driver tried to write a message in the queue that was too big for the queue. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6307 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IPA: Cannot reset connection |
| Long Text: | A fatal error occurred during the resetting of the connection. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6308 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: No more connections available |
| Long Text: | You have exhausted all your connections. |
| Repair Text: | From Oracle doc: Try again when some of the current users have logged off. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: No message queue available |
| Long Text: | The SQL*Net IPA servers have not been started. |
| Repair Text: | From Oracle doc: Run IPACTL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Environment variable(s) not set |
| Long Text: | Environment variable(s) not set correctly. |
| Repair Text: | From Oracle doc: Check and correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Maximum number of servers reached |
| Long Text: | Maximum number of servers reached. |
| Repair Text: | From Oracle doc: Shut down and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start enough servers to support database links. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6312 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Incorrect outgoing service name supplied |
| Long Text: | Incorrect outgoing service name supplied. |
| Repair Text: | From Oracle doc: Check and correct the service name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Shared memory failed to initialise |
| Long Text: | The shared memory has not been set up correctly. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6314 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IPA: Event set up failure |
| Long Text: | Fatal interprocess communication error. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Invalid connect %s |
| Long Text: | The connect string is malformed. |
| Repair Text: | From Oracle doc: Check and correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Invalid database SID |
| Long Text: | The SID is unknown at the remote side. |
| Repair Text: | From Oracle doc: Either the database does not exist, is not running, or there are no reserved servers for that SID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6317 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | IPA: Local maximum number of users exceeded |
| Long Text: | The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the local side. |
| Repair Text: | From Oracle doc: Wait for free connections to become available. If the problem persists, contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6318 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | IPA: Local maximum number of connections exceeded |
| Long Text: | The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side. |
| Repair Text: | From Oracle doc: Wait for free connections to become available. If the problem persists, contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6319 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | IPA: Remote maximum number of users exceeded |
| Long Text: | The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the remote side. |
| Repair Text: | From Oracle doc: Wait for free connections to become available. If the problem persists, contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6320 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | IPA: Remote maximum number of connections exceeded |
| Long Text: | The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side. |
| Repair Text: | From Oracle doc: Wait for free connections to become available. If the problem persists, contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPA: Cannot reach the remote side |
| Long Text: | There has been a timeout on an attempt to connect to a remote server the reason for which is most likely to be the remote SQL*Net IPA software is not running. An alternative reason could be that the remote initiator service name is incorrect. |
| Repair Text: | From Oracle doc: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6322 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IPA: Fatal shared memory error |
| Long Text: | An internal error has occurred in the shared memory handling. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6323 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IPA: Cause event error |
| Long Text: | Fatal interprocess communication error. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: No default host %s specified |
| Long Text: | There was no default host string specified in the configuration and the user did not specify any explicit connect string. |
| Repair Text: | From Oracle doc: Either reconfigure the system specifying a default connect string or use an explicit connect string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: invalid driver designator |
| Long Text: | The login (connect) string contains an invalid driver designator. |
| Repair Text: | From Oracle doc: Correct the string and re-submit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: error receiving break message |
| Long Text: | Error occurred while attempting to read a break message. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to allocate memory. |
| Long Text: | System unable to allocate needed virtual memory. |
| Repair Text: | From Oracle doc: Configure more memory, reduce load, or try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: invalid login (connect) %s |
| Long Text: | Syntax error in login string. |
| Repair Text: | From Oracle doc: Correct string and re-submit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6405 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: reset protocol error |
| Long Text: | Unable to reset out of break state. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: error sending break message |
| Long Text: | Error occurred while attempting to send a break message. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: unable to set up break handling environment |
| Long Text: | Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: incorrect message format |
| Long Text: | Message from partner contains bad header. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6413 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Connection not open. |
| Long Text: | Unable to establish connection. |
| Repair Text: | From Oracle doc: Use diagnostic procedures to ascertain exact problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6416 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: error on test |
| Long Text: | Error occurred while testing I/O status of the network connection. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6419 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: server can not start oracle |
| Long Text: | The remote server was unable to start an Oracle process on behalf of the client. |
| Repair Text: | From Oracle doc: Make sure permissions on the remote Oracle program are correctly set. Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6420 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: SID lookup failure |
| Long Text: | From the remote host's server: the database SID, specified in the login (connect) string, was not recognized. |
| Repair Text: | From Oracle doc: Add the appropriate SID entry to the CONFIG.ORA or ORATAB file on the remote host (restarting the remote server may be needed). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6421 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: Error detected in the read-in data |
| Long Text: | Error found during recomputation of checksum or CRC. |
| Repair Text: | From Oracle doc: Possible hardware failures of communication nodes. Contact system administrator immediately. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6422 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: Error in sending data |
| Long Text: | Unable to transmit data to remote host. |
| Repair Text: | From Oracle doc: Try reconnect to remote host, and contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6423 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NETCMN: Error in receiving data |
| Long Text: | Unable to receive data from remote host. |
| Repair Text: | From Oracle doc: Try reconnect to remote host, and contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: Seals do not match |
| Long Text: | A function was called with an invalid argument. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: Invalid Block number |
| Long Text: | The file block number is out of range of the file. The additional information returns the block number. |
| Repair Text: | From Oracle doc: Verify that the block number is correct. Run DBFSIZE and check if the block number is in that range. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: Buffer Not Aligned |
| Long Text: | The I/O buffer was not aligned on a 2K boundary. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: LSEEK error, unable to seek to requested block. |
| Long Text: | The additional information returns the block number. |
| Repair Text: | From Oracle doc: Look up the additional information returned in your operating system reference manual. Verify that the block number is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6434 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: read error, unable to read requested block from database file. |
| Long Text: | The read system call returned an error. |
| Repair Text: | From Oracle doc: The additional information indicates the block number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6435 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: write error, unable to write requested block to database file. |
| Long Text: | The write system call returned an error. |
| Repair Text: | From Oracle doc: The additional information indicates the block number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: asynchronous I/O failed due to incorrect parameters. |
| Long Text: | The Asynchronous I/O system call returned an error. |
| Repair Text: | From Oracle doc: The additional information indicates the block number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: the asynchronous write was unable to write to the database file. |
| Long Text: | The Asynchronous I/O system call returned an error. |
| Repair Text: | From Oracle doc: The additional information indicates the block number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: the asynchronous read was unable to read from the database file. |
| Long Text: | The Asynchronous I/O system call returned an error. |
| Repair Text: | From Oracle doc: The additional information indicates the block number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6439 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: the asynchronous write returned incorrect number of bytes |
| Long Text: | This write call may have been truncated. The additional information returns the block number and number of bytes. |
| Repair Text: | From Oracle doc: Verify that the block number and the number of bytes written are correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssaio: the asynchronous read returned incorrect number of bytes |
| Long Text: | This read call may have been truncated. The additional information returns the block number and number of bytes. |
| Repair Text: | From Oracle doc: Verify that the block number and the number of bytes read are correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvwatev: Incorrect parameter passed to function call |
| Long Text: | Either the Oracle process ID, or wait time or event ID is invalid. |
| Repair Text: | From Oracle doc: The additional information indicates the process ID, time and event ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6442 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvwatev: Failed with unexpected error number. |
| Long Text: | Some system problems may exist on your system; check the error logs. |
| Repair Text: | From Oracle doc: The additional information indicates the error number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvpstev: Incorrect parameter passed to function call |
| Long Text: | An invalid event ID is passed in to this routine. |
| Repair Text: | From Oracle doc: The additional information indicates the event ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvpstev: Failed with unexpected error number. |
| Long Text: | Some system problems may exist on your system; check the error logs. |
| Repair Text: | From Oracle doc: The additional information indicates the error number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6445 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvpstevrg: Incorrect parameters passed to function call |
| Long Text: | An invalid event ID, or the low and high event ID do not exist. |
| Repair Text: | From Oracle doc: The additional information indicates the error number. It also contains the event ID, low boundary and high boundary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvpstevrg: Failed with unexpected error number. |
| Long Text: | Some system problems may exist on your system; check the error logs. |
| Repair Text: | From Oracle doc: The additional information indicates the error number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6447 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvpstp: Incorrect parameter passed to function call |
| Long Text: | Invalid Oracle process ID is passed in to this routine. |
| Repair Text: | From Oracle doc: The additional information indicates the process ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6448 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssvpstp: Failed with unexpected error number. |
| Long Text: | Some system problems may exist on your system; check the error logs. |
| Repair Text: | From Oracle doc: The additional information indicates the error number. Look up the additional information returned in your operating system manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The list IO or the sysvendor is not installed. |
| Long Text: | Oracle tries to use the SYSVENDOR interface (INIT.ORA parameter USE_SYSVENDOR=TRUE) but the UNIX kernel does not have the Oracle SYSVENDOR interface linked in. |
| Repair Text: | From Oracle doc: Set USE_SYSVENDOR=FALSE in INIT.ORA, if you do not want to use this interface or link the UNIX kernel with this interface so that Oracle can use it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: storage error |
| Long Text: | This is a rare internal error message. Memory has been exhausted or corrupted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: program error |
| Long Text: | This is an internal error message. An error has been detected in a PL/SQL program. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: numeric or value error%s |
| Long Text: | An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2). |
| Repair Text: | From Oracle doc: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: Function returned without value |
| Long Text: | A call to PL/SQL function completed, but no RETURN statement was executed. |
| Repair Text: | From Oracle doc: Rewrite PL/SQL function, making sure that it always returns a value of a proper type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: Return types of Result Set variables or query do not match |
| Long Text: | Number and/or types of columns in a query does not match declared return type of a result set variable, or declared types of two Result Set variables do not match. |
| Repair Text: | From Oracle doc: Change the program statement or declaration. Verify what query the variable actually refers to during execution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: variable requires more than 32767 bytes of contiguous memory |
| Long Text: | A PL/SQL variable was declared with a constraint which required more than 32767 bytes of memory. PL/SQL does not currently support allocations of contiguous memory greater than 32767 bytes. |
| Repair Text: | From Oracle doc: Consider reducing the constraint in the variable declaration. If that is not possible, try changing the database or national character set to such, that requires less memory for the same constraint. Note: changing the character set will impact execution of all PL/SQL code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: could not find program unit being called |
| Long Text: | An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors. |
| Repair Text: | From Oracle doc: Check that all referenced programs, including their package bodies, exist and are compatible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: ICD vector missing for this package |
| Long Text: | This indicates a version clash between some package distributed with an Oracle product and the product executable. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: unhandled user-defined exception |
| Long Text: | A user-defined exception was raised by PL/SQL code, but not handled. |
| Repair Text: | From Oracle doc: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: cursor already open |
| Long Text: | An attempt was made to open a cursor that was already open. |
| Repair Text: | From Oracle doc: Close cursor first before reopening. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | at stringline %s |
| Long Text: | Backtrace message as the stack is unwound by unhandled exceptions. |
| Repair Text: | From Oracle doc: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: index for PL/SQL table out of range for host language array |
| Long Text: | An attempt is being made to copy a PL/SQL table to a host language array. But an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, etc. If an table entry has not been assigned then the corresponding element in the host language array is set to null. |
| Repair Text: | From Oracle doc: Increase size of host language array, or decrease size of PL/SQL table. Also make sure that you do not use index values less than 1. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: The remote call cannot be handled by the server |
| Long Text: | The remote call has parameters that are cursor variables. This cannot be handled by stored procedures on your server. |
| Repair Text: | From Oracle doc: Avoid using cursor variables as parameters for stored procedures on this server or upgrade your server to a version that supports this. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6515 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: unhandled exception %s |
| Long Text: | An exception was raised by PL/SQL code, but not handled. The exception number is outside the legal range of Oracle errors. |
| Repair Text: | From Oracle doc: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6516 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: the Probe packages do not exist or are invalid |
| Long Text: | A Probe operation, probably an attempt to initialize the Oracle server to debug PL/SQL, could not be completed because the Probe packages were not loaded or have become invalid. |
| Repair Text: | From Oracle doc: DBA should load the Probe packages. This can be done by running the PBLOAD.SQL script supplied with the RDBMS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6517 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: Probe error - %s |
| Long Text: | An error occurred while passing a Probe operation to the server for execution. |
| Repair Text: | From Oracle doc: Refer to the entry for the embedded error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6518 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: Probe version %s incompatible with version %s |
| Long Text: | The current version of Probe is incompatible with the version on the Oracle server. |
| Repair Text: | From Oracle doc: Refer to the documentation to ensure that this degree of compatibility is supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6519 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | active autonomous transaction detected and rolled back |
| Long Text: | Before returning from an autonomous PL/SQL block, all autonomous transactions started within the block must be completed (either committed or rolled back). If not, the active autonomous transaction is implicitly rolled back and this error is raised. |
| Repair Text: | From Oracle doc: Ensure that before returning from an autonomous PL/SQL block, any active autonomous transactions are explicitly committed or rolled back. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6520 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: Error loading external library |
| Long Text: | An error was detected by PL/SQL trying to load the external library dynamically. |
| Repair Text: | From Oracle doc: Check the stacked error (if any) for more details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6521 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: Error mapping function |
| Long Text: | An error was detected by PL/SQL trying to map the mentioned function dynamically. |
| Repair Text: | From Oracle doc: Check the stacked error (if any) for more details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6522 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | ORA-06520 or ORA-06521could stack this error with a system-specific error string. |
| Repair Text: | From Oracle doc: This error string should give the cause for errors ORA-06520 or ORA-06521 |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6523 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Maximum number of arguments exceeded |
| Long Text: | There is an upper limit on the number of arguments that one can pass to the external function. |
| Repair Text: | From Oracle doc: Check the port-specific documentation on how to calculate the upper limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6524 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Unsupported option : %s |
| Long Text: | The option specified is an unsupported feature for external procedures. |
| Repair Text: | From Oracle doc: Correct the syntax in the external specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6525 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Length Mismatch for CHAR or RAW data |
| Long Text: | The length specified in the length variable has an illegal value. This can happen if you have requested a PL/SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with no corresponding length variable. This error can also happen if there is a mismatch in the length value set in the length variable and the length in the ORLVSTR or ORLRAW. |
| Repair Text: | From Oracle doc: Correct the external procedure code and set the length variable correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6526 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to load PL/SQL library |
| Long Text: | PL/SQL was unable to instantiate the library referenced by this referenced in the EXTERNAL syntax. This is a serious error and should normally not happen. |
| Repair Text: | From Oracle doc: Report this problem to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6527 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | External procedure SQLLIB error: %s |
| Long Text: | An error occurred in SQLLIB during execution of a Pro* external procedure. |
| Repair Text: | From Oracle doc: The message text indicates the actual SQLLIB error that occurred. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6528 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error executing PL/SQL profiler |
| Long Text: | An error occurred during execution of a PL/SQL profiler procedure. |
| Repair Text: | From Oracle doc: Check the stacked errors for more details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6529 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Version mismatch - PL/SQL profiler |
| Long Text: | The PL/SQL profiler package (DBMSPB.SQL, PRVTPBP.PLB) does not match the version of the code in the server implementing the profiler. |
| Repair Text: | From Oracle doc: Run the package PROFLOAD.SQL in $ORACLE_HOME/rdbms/admin to load the correct version of the PL/SQL profiler packages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6530 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Reference to uninitialized composite |
| Long Text: | An object, LOB, or other composite was referenced as a left hand side without having been initialized. |
| Repair Text: | From Oracle doc: Initialize the composite with an appropriate constructor or whole-object assignment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6531 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Reference to uninitialized collection |
| Long Text: | An element or member function of a nested table or VARRAY was referenced (where an initialized collection is needed) without the collection having been initialized. |
| Repair Text: | From Oracle doc: Initialize the collection with an appropriate constructor or whole-object assignment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6532 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Subscript outside of limit |
| Long Text: | A subscript was greater than the limit of a VARRAY or non-positive for a VARRAY or nested table. |
| Repair Text: | From Oracle doc: Check the program logic and increase the VARRAY limit if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6533 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Subscript beyond count |
| Long Text: | An in-limit subscript was greater than the count of a VARRAY or too large for a nested table. |
| Repair Text: | From Oracle doc: Check the program logic and explicitly extend if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot access Serially Reusable package %s in the context of a trigger |
| Long Text: | The program attempted to access a Serially Reusable package in the context of a trigger. Such an access is currently unsupported. |
| Repair Text: | From Oracle doc: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen in the context of a trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6535 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | statement %s in %s is NULL or 0 length |
| Long Text: | The program attempted to use a dynamic statement string that was either NULL or 0 length. |
| Repair Text: | From Oracle doc: Check the program logic and ensure that the dynamic statement string is properly initialized. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6536 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IN bind variable bound to an OUT position |
| Long Text: | The program attempted to bind an IN bind variable to a statement that was expecting an OUT bind variable at that position. |
| Repair Text: | From Oracle doc: Make sure that an OUT or IN OUT bind mode is specified for the bind argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6537 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OUT bind variable bound to an IN position |
| Long Text: | The program attempted to bind an OUT bind variable to a statement that was expecting an IN bind variable at that position. |
| Repair Text: | From Oracle doc: Make sure that an IN or IN OUT bind mode is specified for the bind argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6538 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | statement violates %s RESTRICT_REFERENCES pragma |
| Long Text: | The program attempted to execute a dynamic statement which does not meet the purity level specified (in the pragma RESTRICT_REFERENCES directive) for the module executing the statement. |
| Repair Text: | From Oracle doc: Ensure that the dynamic statement meets the purity level specified for the module executing the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6539 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | target of OPEN must be a query |
| Long Text: | The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query. |
| Repair Text: | From Oracle doc: Ensure that the OPEN cursor operation is done on a dynamic query statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6540 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: compilation error |
| Long Text: | A PL/SQL compilation error occurred. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages. |
| Repair Text: | From Oracle doc: See accompanying PLS-nnnnn error messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6541 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: compilation error - compilation aborted |
| Long Text: | A PL/SQL compilation error occurred and the compilation was aborted; but the compilation unit was written out to the backing store. However, unlike ORA-06545, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages. |
| Repair Text: | From Oracle doc: See accompanying PLS-nnnnn error messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6542 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DDL statement is executed in an illegal context |
| Long Text: | DDL statement is executed dynamically in illegal PL/SQL context: Dynamic OPEN cursor for a DDL in PL/SQL Bind variables used in USING clause to EXECUTE IMMEDIATE a DDL Define variables used in INTO clause to EXECUTE IMMEDIATE a DDL |
| Repair Text: | From Oracle doc: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the DDL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6543 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RETURNING clause must be used with INSERT, UPDATE, or DELETE statements |
| Long Text: | EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only. |
| Repair Text: | From Oracle doc: Use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other statements, use USING clause instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6544 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s] |
| Long Text: | A PL/SQL internal error occurred. |
| Repair Text: | From Oracle doc: Report as a bug; the first argument is the internal error number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6545 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: compilation error - compilation aborted |
| Long Text: | A PL/SQL compilation error occurred and the compilation was aborted completely without the compilation unit being written out to the backing store. Unlike ORA-06541, the user will always see this error along with the accompanying PLS-nnnnn error messages. |
| Repair Text: | From Oracle doc: See accompanying PLS-nnnnn error messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6550 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | line %s, column %s:%s |
| Long Text: | A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred. |
| Repair Text: | From Oracle doc: Refer to the following PL/SQL messages for more information about the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: Unhandled exception |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PL/SQL: %s |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6553 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PLS-%s: %s |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6554 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | package DBMS_STANDARD must be created before using PL/SQL |
| Long Text: | The DBMS-specific extensions to PL/SQL's package STANDARD are in package DBMS_STANDARD. This package must be created before using PL/SQL. |
| Repair Text: | From Oracle doc: Create package DBMS_STANDARD. The source for this PL/SQL stored package is provided with the distribution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6555 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this name is currently reserved for use by user SYS |
| Long Text: | An attempt was made to create a package named STANDARD, DBMS_STANDARD or DEBUG_IO. These are currently reserved for use by user SYS. |
| Repair Text: | From Oracle doc: Choose another name for your package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6556 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the pipe is empty, cannot fulfill the unpack_message request |
| Long Text: | There are no more items in the pipe. |
| Repair Text: | From Oracle doc: Check that the sender and receiver agree on the number and types of items placed on the pipe. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6557 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null values are not allowed for any parameters to pipe icd's |
| Long Text: | Internal error from the DBMS_PIPE package. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6558 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buffer in dbms_pipe package is full. No more items allowed |
| Long Text: | The pipe buffer size has been exceeded. |
| Repair Text: | From Oracle doc: Inspect the program to analyze the rate of input and output to the pipe. You might need to take items out of the pipe by executing RECEIVE_MESSAGE, or empty the entire pipe by executing PURGE on the pipe. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6559 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong datatype requested, %s, actual datatype is %s |
| Long Text: | The sender put different datatype on the pipe than that being requested (package DBMS_PIPE). The numbers are: 6 - number 9 - char 12 - date |
| Repair Text: | From Oracle doc: Check that the sender and receiver agree on the number and types of items placed on the pipe. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6560 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pos, %s, is negative or larger than the buffer size, %s |
| Long Text: | Internal error from the DBMS_PIPE package. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6561 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | given statement is not supported by package DBMS_SQL |
| Long Text: | An attempt was made to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL. |
| Repair Text: | From Oracle doc: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6562 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type of out argument must match type of column or bind variable |
| Long Text: | An attempt was made to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL but the type of the given out argument where to place the value is different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN (for defining a column) or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL. |
| Repair Text: | From Oracle doc: Pass in an out argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6563 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | top level procedure/function specified, cannot have subparts |
| Long Text: | The name to be resolved was specified with three parts (a.b.c) but the a.b part resolves to a top level procedure or function (which do not have nested procedures). This can also happen with a two-part name, a.b, where a is a synonym for a top level package or procedure. |
| Repair Text: | From Oracle doc: Specify a procedure/function within a package, or a top level procedure/function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6564 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s does not exist |
| Long Text: | The named object could not be found. Either it does not exist or you do not have permission to access it. |
| Repair Text: | From Oracle doc: Create the object or get permission to access it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6565 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot execute %s from within stored procedure |
| Long Text: | The named procedure cannot be executed from within a stored procedure, function or package. This function can only be used from PL/SQL anonymous blocks. |
| Repair Text: | From Oracle doc: Remove the procedure from the calling stored procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6566 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number of rows specified |
| Long Text: | An invalid number of rows was specified in a call to the procedure DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number of rows. |
| Repair Text: | From Oracle doc: Specify a number that matches that for previously defined columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6567 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number of values specified |
| Long Text: | An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. In order to execute a given parsed statement in a given cursor, the same number of values must have been bound for all bind variables, so when EXECUTE is called, the latest calls to BIND_VARIABLE must have specified the same number of values to be bound for all bind variables. |
| Repair Text: | From Oracle doc: Make sure that the same number of values have been bound for all of the bind variables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6568 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | obsolete ICD procedure called |
| Long Text: | An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an earlier release of RDBMS. |
| Repair Text: | From Oracle doc: Make sure that all PL/SQL programs have been upgraded to the latest release of the RDBMS. This can be accomplished by following upgrade instructions in the README file, or by running the CATPROC.SQL script supplied with the RDBMS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6569 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Collection bound by bind_array contains no elements |
| Long Text: | A collection with zero elements was bound to a bind variable in a call to procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a collection, the collection must contain at least one element. If no elements are present then at execute time there will be no value for this bind and the statement is meaningless. |
| Repair Text: | From Oracle doc: Fill the collection with the elements you want to bind and try the bind call again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6570 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | shared pool object does not exist, cannot be pinned |
| Long Text: | The specified shared pool shared cursor could not be found, therefore it cannot be pinned. |
| Repair Text: | From Oracle doc: Make sure that a correct shared cursor name is given. Names are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's are an 8 digit hex number from the 'address' column of V$SQLAREA, and the D's are a 1 to 10 digit decimal number with an optional leading sign (from the HASH_VALUE column) Remove the procedure from the calling stored procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6571 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Function %s does not guarantee not to update database |
| Long Text: | One of the following: A SQL statement references a packaged, PL/SQL function that does not contain a pragma that prevents the database from being updated. A SQL statement references a standalone, PL/SQL function that contains an instruction to update the database. |
| Repair Text: | From Oracle doc: If the referenced function is a packaged, PL/SQL function, re-create the PL/SQL function with the required pragma; be certain to include the 'Write No Database State' (WNDS) argument in the argument list of the pragma. If the referenced function is standalone, PL/SQL function, do not use the function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6572 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Function %s has out arguments |
| Long Text: | A SQL statement references either a packaged or standalone PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter. |
| Repair Text: | From Oracle doc: Re-create the PL/SQL function without the OUT parameter in the argument list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6573 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Function %s modifies package state, cannot be used here |
| Long Text: | One of the following: A SQL statement references a packaged, PL/SQL function that does not contain a pragma containing the 'Write no Package State' (WNPS). A SQL statement references a standalone, PL/SQL function that modifies a package state. A standalone, PL/SQL function referenced by a SQL statement cannot modify a package state. |
| Repair Text: | From Oracle doc: If the function is a packaged, PL/SQL function: Re-create the function and include a pragma containing the 'Write no Package State' (WNPS). If the function is standalone PL/SQL function, delete the function from the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6574 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Function %s references package state, cannot execute remotely |
| Long Text: | One of the following: A remote, packaged function or a remote-mapped, local, packaged function that does not contain a pragma with the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments references a package state. A remote, standalone function or a remote-mapped, local, standalone function contains a reference to a package state (reads or writes a package variable). Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state. |
| Repair Text: | From Oracle doc: If the function is a packaged function: Re-create the function and include a pragma containing the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments. If the function is a standalone function: Do not call the function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6575 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Package or function %s is in an invalid state |
| Long Text: | A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors. |
| Repair Text: | From Oracle doc: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6576 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a function or procedure |
| Long Text: | Could not find a function (if an INTO clause was present) or a procedure (if the statement did not have an INTO clause) to call. |
| Repair Text: | From Oracle doc: Change the statement to invoke a function or procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6577 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | output parameter not a bind variable |
| Long Text: | The argument corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement must be a bind variable. |
| Repair Text: | From Oracle doc: Change the argument to a bind variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6578 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | output parameter cannot be a duplicate bind |
| Long Text: | The bind variable corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement cannot be a duplicate bind variable. |
| Repair Text: | From Oracle doc: Change the bind variable to be unique. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6580 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Hash Join ran out of memory while keeping large rows in memory |
| Long Text: | Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised. |
| Repair Text: | From Oracle doc: Increase HASH_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increased. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: SNA software is not loaded |
| Long Text: | The SNA software is not running. |
| Repair Text: | From Oracle doc: Start the SNA software and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Invalid database ID %s |
| Long Text: | The database string in the connect was invalid. |
| Repair Text: | From Oracle doc: Provide a valid database string, as defined in documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6602 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Error allocating context area |
| Long Text: | Context area failure. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6603 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Error allocating memory |
| Long Text: | Operating system refused request for memory. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6604 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Unable to allocate session with remote LU |
| Long Text: | Allocate system call failed. |
| Repair Text: | From Oracle doc: Ensure that the SNA software is running and that sessions are free. If this is the case, then check your SNA configuration data for errors. You may have entered an incorrect parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6605 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Unexpected line turnaround |
| Long Text: | SNA software switched from send to receive unexpectedly. |
| Repair Text: | From Oracle doc: Check the SNA configuration data, particularly parameters associated with a session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Unexpected response from SNA |
| Long Text: | A parameter in an SNA call returned an unexpected value. |
| Repair Text: | From Oracle doc: Attempt to reproduce problem, debug and record the value of the 'what' data parameter at the time of error. Then contact your service representative. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6607 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Reset occurred in send state |
| Long Text: | A reset was issued while in send state. |
| Repair Text: | From Oracle doc: Check the SNA LOG data, if relevant, for further information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6608 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Reset occurred in receive state |
| Long Text: | A reset was received from the partner while in receive state. This may be because the partner deallocated. |
| Repair Text: | From Oracle doc: Check the SNA LOG data, if relevant, for further information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6610 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Failed during deallocation |
| Long Text: | LU6.2 driver was unable to deallocate gracefully. |
| Repair Text: | From Oracle doc: Check the reason for deallocation. Consult the SNA LOG data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6611 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Request to send error |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6612 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Send data error |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6613 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Receive and wait error |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6614 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Receive Immediate error |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6615 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Send error |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6616 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Attach to LU failed |
| Long Text: | The SQL*Net LU6.2 driver was unable to attach to the LU specified in the connect string, or was unable to attach to the default LU. |
| Repair Text: | From Oracle doc: Check that the LU name specified in the connect string, or the default LU name if no LU was specified, is correctly configured and operational. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6617 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Attach to PU failed |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6618 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Activation of subnetwork failed |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6619 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Unable to activate remote partner |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6620 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Invalid remote partner |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6621 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Allocation error |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6622 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LU6.2 Driver: Unable to attach to SNA |
| Long Text: | The SQL*Net LU6.2 driver could not attach to the SNA software on your machine. The most likely cause is that the SNA software is not operational. |
| Repair Text: | From Oracle doc: Check the status of the SNA software, ensure that it is operational and then try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6700 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: incorrect message type from host |
| Long Text: | TLI received a message with an unrecognizable message type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: incorrect number of bytes written |
| Long Text: | TLI sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes supplied to the driver. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot allocate context area |
| Long Text: | TLI could not allocate heap space for the context area. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: send break message failed |
| Long Text: | TLI failed to send a break message across the connection. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: receive break message failed |
| Long Text: | TLI failed to receive an expected break message. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: remote node is unknown |
| Long Text: | TLI could not find your remote host information. |
| Repair Text: | From Oracle doc: Make sure you specified the host name correctly on the command line. (Also, check your capitalization and spelling.) |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: service not found |
| Long Text: | TLI could not find service information for the specified service name. |
| Repair Text: | From Oracle doc: If you specified the service name on the command line or with the environment variable TLI_SERVER, make sure you specified it correctly. If the service name is not in the SERVICES file for your protocol, ask your system administrator to add it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6707 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: connection failed |
| Long Text: | TLI failed to establish the connection to a SQL*Net TCP/IP server due to an error encountered by the remote server, which has supplied a string describing the remote error. |
| Repair Text: | From Oracle doc: See the SQL*Net TCP/IP User's Guide or the Net8 Administrator's Guide for the specific cause and action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: message receive failure |
| Long Text: | TLI encountered an error receiving a message from the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: message send failure |
| Long Text: | TLI encountered an error sending a message across the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6710 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: send interrupt break message failed |
| Long Text: | TLI failed to send a break message while handling an interrupt signal from the user. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6711 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error on bind |
| Long Text: | TLI failed to assign a network address to the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6712 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error on accept |
| Long Text: | TLI failed to accept a connection request from the client. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6713 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error on connect |
| Long Text: | TLI failed to connect the client to the remote server. The network line to the remote host may be down. |
| Repair Text: | From Oracle doc: Use other network login programs to make sure that the remote host is accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6720 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: SID lookup failure |
| Long Text: | The database SID supplied in the database login string was not recognized by the remote host. |
| Repair Text: | From Oracle doc: Ask your system administrator to add the appropriate SID entry to ORATAB on the remote host. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6721 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: spurious client req |
| Long Text: | The remote TLI server received an undefined request. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6722 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: connection setup failure |
| Long Text: | The remote TLI server rejected the connection request, and the client was unable to retrieve an error code or message. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6730 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: unable to open clone device |
| Long Text: | TLI failed to open the Streams clone device associated with the transport provider. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6731 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot alloc t_call |
| Long Text: | TLI cannot allocate space for the client's connection information. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6732 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot alloc t_discon |
| Long Text: | TLI cannot allocate space for the client's disconnection information. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6733 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: failed to receive disconnect |
| Long Text: | TLI failed to receive an expected disconnection message during connection release. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6734 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot connect |
| Long Text: | TLI failed to connect the client to the remote server. |
| Repair Text: | From Oracle doc: Check that the remote TLI server is running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6735 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: client failed to close error conn |
| Long Text: | TLI failed to properly close a connection after an error was received. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6736 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: server not running |
| Long Text: | TLI timed out while attempting to connect to the remote TLI server. |
| Repair Text: | From Oracle doc: Check that the remote TLI server is running with the status utility for the transport provider you are using. If it is not, ask your system administrator to start it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6737 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: connection failed |
| Long Text: | TLI could not establish a connection to the remote TLI server. |
| Repair Text: | From Oracle doc: Check that the remote TLI server is running with the status utility for the transport provider you are using. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6741 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: unable to open protocol device |
| Long Text: | The TLI server failed to open the Streams device associated with the transport provider. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6742 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot alloc t_bind |
| Long Text: | The TLI server cannot allocate space for its requested network address. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6743 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot alloc t_bind |
| Long Text: | The TLI server cannot allocate space for its actual network address. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6744 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: listener cannot bind |
| Long Text: | The TLI server failed to assign the correct network address on which to listen for connections. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6745 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: listener already running |
| Long Text: | The network address on which the TLI server awaits connection requests is in use, possibly because the server is already running. |
| Repair Text: | From Oracle doc: Ensure that the TLI server is not already running. If it is not running and this error message recurs, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6746 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot alloc t_call |
| Long Text: | TLI cannot allocate space for the TLI server's connection information. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6747 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error in listen |
| Long Text: | The TLI server encountered an error while listening for connection requests. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6748 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot allocate t_discon |
| Long Text: | TLI cannot allocate space for the TLI server's disconnection information. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6749 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: option not allowed across network |
| Long Text: | The requested TLI server command must be issued from the same host on which the server is running. |
| Repair Text: | From Oracle doc: Log in to the remote host and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6750 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: sync failed |
| Long Text: | The Oracle process started by the TLI server was unable to synchronize its inherited connection. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6751 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: bound addresses unequal |
| Long Text: | The OSN check server address failed. The bound server address was not the same as the requested binding address. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6752 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI: error in signal setup |
| Long Text: | A call to SIGACTION() returned with a system error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6753 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: name-to-address mapping failed |
| Long Text: | For SVR4, the NETDIR_GETBYNAME() call failed for some unknown reason. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6754 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: unable to get local host address |
| Long Text: | The name of the remote host to connect to was not specified, and the name of the local host cannot be retrieved from the HOSTS file. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6755 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot close transport endpoint |
| Long Text: | The TLI server was unable to close a connection after passing it to an Oracle process. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6756 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: cannot open oratab |
| Long Text: | The TLI server could not open the file used to define the locations of remotely accessible databases. |
| Repair Text: | From Oracle doc: Ask your system administrator to check that the file exists and has the correct permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6757 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: server got bad command |
| Long Text: | The TLI server received an invalid command. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6760 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: timeout reading orderly release |
| Long Text: | TLI was not able to retrieve an expected disconnect message while closing the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6761 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error sending orderly release |
| Long Text: | TLI encountered an error sending a disconnect message closing the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6762 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading orderly release |
| Long Text: | TLI encountered an error receiving an expected disconnect message while closing the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6763 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error sending disconnect |
| Long Text: | TLI encountered an error sending a disconnect message closing the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6764 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading disconnect |
| Long Text: | TLI was not able to retrieve an expected disconnect message while closing the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6765 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error awaiting orderly release |
| Long Text: | TLI encountered an error awaiting a disconnect message while closing the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6766 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: close failed during release |
| Long Text: | TLI failed to close the communication channel after receiving a disconnect message. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6767 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: alloc failed during release |
| Long Text: | TLI cannot allocate space for disconnection information while closing the communication channel. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6770 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error sending version |
| Long Text: | TLI encountered an error while sending its version information during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6771 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading version |
| Long Text: | TLI encountered an error while awaiting the expected version information during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6772 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error sending command |
| Long Text: | TLI encountered an error while sending a command message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6773 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading command |
| Long Text: | TLI encountered an error while awaiting the expected command message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6774 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error sending break mode |
| Long Text: | TLI encountered an error while sending break-mode message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6775 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading break mode |
| Long Text: | TLI encountered an error while awaiting the expected break-mode message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6776 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error sending parms |
| Long Text: | TLI encountered an error while sending the connection parameters during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6777 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading parms |
| Long Text: | TLI encountered an error while awaiting the expected connection parameter message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6778 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error sending ccode |
| Long Text: | TLI encountered an error while sending the completion status message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6779 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading ccode |
| Long Text: | TLI encountered an error while awaiting the expected completion status message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6780 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: recv error code failed |
| Long Text: | TLI encountered an error while awaiting an expected error message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6781 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: error reading negotation %s |
| Long Text: | TLI encountered an error while awaiting the expected negotiation message during connection establishment. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6790 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: poll failed |
| Long Text: | TLI was unable to poll the communication channel for possible incoming messages. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6791 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: poll returned error event |
| Long Text: | TLI received an unexpected event while polling the communication channel for possible incoming messages. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6792 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: server cannot exec oracle |
| Long Text: | The remote TLI server was unable to start an Oracle process on behalf of the client. |
| Repair Text: | From Oracle doc: Note the operating system error message or number and contact your system administrator. The permissions on the remote Oracle program may be set incorrectly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6793 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: server cannot create new process |
| Long Text: | The remote TLI server was unable to start an Oracle process on behalf of the client. |
| Repair Text: | From Oracle doc: Note the operating system error message or number and contact your system administrator. The remote host may be unable to create any new processes due to a full process table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6794 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: shadow process could not retrieve protocol info |
| Long Text: | The Oracle process either failed to allocate memory to store the protocol information record, or the protocol rejected the request for some unknown reason. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: SQL*Net SPX client went away during reconnect |
| Long Text: | The client process was aborted by the system or the user, and was unable to complete the connection establishment with the server listener process. |
| Repair Text: | From Oracle doc: Determine the cause of the client exit, and reattempt the connection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: listen for SPX server reconnect failed |
| Long Text: | An unknown event occurred on the client's listening socket. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not open the /etc/netware/yellowpages file |
| Long Text: | The /etc/netware/yellowpages file does not exist, or is not readable by the TLI listener process. |
| Repair Text: | From Oracle doc: Insure the file exists and is readable. Make sure that the server machine's node name, network number, ethernet address, and listening socket number are encoded in the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: the IPX device file could not be opened |
| Long Text: | The /dev/ipx file does not exist, or the driver has not been installed in the kernel correctly. |
| Repair Text: | From Oracle doc: Reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not bind an IPX address at initialization |
| Long Text: | The IPX driver has not been correctly installed. |
| Repair Text: | From Oracle doc: Reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6805 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not send datagram SAP packet for SPX |
| Long Text: | The socket endpoint for sending SAP packet was corrupted for some unknown reason. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6806 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not complete protocol initialization for SPX |
| Long Text: | A step in the SPX/IPX protocol initialization failed. |
| Repair Text: | From Oracle doc: Check the previous error reported, and follow corrective action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6807 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not open ethernet device driver file |
| Long Text: | The file /dev/eth does not exist, or the driver it references could not be opened. |
| Repair Text: | From Oracle doc: The system's real ethernet device file, for example /dev/wd, for the Western Digital ethernet driver, should be linked to the file /dev/eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact Oracle Customer Support for a list of supported ethernet drivers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6808 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not link IPX and ethernet streams |
| Long Text: | Either the ethernet driver has not been installed in the system correctly, or the ethernet driver is not supported. |
| Repair Text: | From Oracle doc: Insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact Oracle Customer Support for a list of supported ethernet drivers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6809 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not clear the IPX ethernet SAP at init |
| Long Text: | The IPX driver has not been correctly installed. |
| Repair Text: | From Oracle doc: Reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not set the IPX ethernet SAP at init |
| Long Text: | The IPX driver has not been correctly installed. |
| Repair Text: | From Oracle doc: Reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not set the IPX network number at init |
| Long Text: | The IPX driver has not been correctly installed, or the network number encoded in the /etc/netware/yellowpages file is invalid. |
| Repair Text: | From Oracle doc: The network number in the yellowpages file should match the four-byte network number of your Novell file server. If this is configured correctly, reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not read the ethernet driver's node address |
| Long Text: | The ethernet driver is not installed correctly, or does not support this operation. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support for a list of supported ethernet drivers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: the configured ethernet address is incorrect |
| Long Text: | The node address read from the ethernet driver does not match the value encoded in the /etc/netware/yellowpages file for this server. |
| Repair Text: | From Oracle doc: Confirm the correct ethernet node address for your LAN card, and enter this value in the yellowpages file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6814 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: the SPX device file could not be opened |
| Long Text: | The /dev/nspxd file does not exist, or the driver has not been installed in the kernel correctly. |
| Repair Text: | From Oracle doc: Reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6815 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not link SPX and IPX streams |
| Long Text: | The SPX driver has not been correctly installed. |
| Repair Text: | From Oracle doc: Reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not set the SPX SAP address |
| Long Text: | The SPX driver has not been correctly installed. |
| Repair Text: | From Oracle doc: Reinvoke the Oracle root installation. If problem continues, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6817 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TLI Driver: could not read the Novell network address |
| Long Text: | The file $ORACLE_HOME/spx/address could not be opened for reading and writing. |
| Repair Text: | From Oracle doc: Make sure ORACLE_HOME is set, and the permissions on the ORACLE_HOME are read, write. If this file has been unintentionally deleted, run SPXCTL (net option) to reset the configured Novell network number for SQL*Net SPX. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6900 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: cannot read tns directory |
| Long Text: | CMX is not started on your system. |
| Repair Text: | From Oracle doc: Install and/or start CMX on your system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6901 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: no local name assigned to local application |
| Long Text: | Local application ORACMX has no local name assigned. |
| Repair Text: | From Oracle doc: Enter unique local name for ORACMX in the TNS directory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6902 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: cannot attach to cmx subsystem |
| Long Text: | CCP-xxxx is not started. |
| Repair Text: | From Oracle doc: Start your CCP software on the communication controller. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6903 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: cannot read transport address of remote application |
| Long Text: | Remote application not entered in TNS directory. |
| Repair Text: | From Oracle doc: Enter remote application in TNS directory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6904 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: no transport address available for remote application |
| Long Text: | No local name assigned to remote application. |
| Repair Text: | From Oracle doc: Assign local name to remote application. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6905 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: connect error |
| Long Text: | Remote partner not listening. |
| Repair Text: | From Oracle doc: Make sure remote node has CMX installed and running make sure ORACMX is running on remote host. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6906 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: cannot get maximum packet size from CMX |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6907 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error during connect confirmation |
| Long Text: | Remote partner aborted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6908 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error during transfer of ORACLE_SID |
| Long Text: | Remote partner aborted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6909 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error during acknowledge of ORACLE_SID |
| Long Text: | Remote partner aborted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6910 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: Cannot start oracle process on remote machine |
| Long Text: | Oracle process not found or wrong mode (should be 4751). |
| Repair Text: | From Oracle doc: Change /etc/oratab or set mode to 4751. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6911 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: t_event returns ERROR |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6912 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: write error in datarq |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6913 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error during redirection of connection |
| Long Text: | ORACMX has been stopped, or user process has been aborted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6914 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: unexepected event during start of oracle |
| Long Text: | Connect sequence out of sync. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6915 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: unknown t_event in datarq |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6916 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error in data read (t_datain) |
| Long Text: | Remote partner aborted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6917 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error in data read (too many bytes read) |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6918 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: T_NOEVENT during wait for read event |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6919 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error during write request (unknown event) |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6920 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: getbrkmsg illegal datatype |
| Long Text: | Received packets are corrupted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6921 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: getdatmsg illegal datatype |
| Long Text: | Received packets are corrupted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6922 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: bad write length |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6923 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: illegal break condition |
| Long Text: | Break handling out of sync. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6924 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: wrong break message length |
| Long Text: | Received packets are corrupted. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6925 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: disconnect during connect request |
| Long Text: | Partner is not responding. |
| Repair Text: | From Oracle doc: Make sure partner is up and running and reachable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6926 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: T_ERROR during read data |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6927 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: T_DATAIN received before all data written |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6928 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: wrong ORACLE_SID |
| Long Text: | ORACLE_SID is not entered in remote ORATAB. |
| Repair Text: | From Oracle doc: add ORACLE_SID to remote ORATAB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6929 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error when sending ORACLE_SID |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6930 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error when checking ORACLE_SID |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6931 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error during read_properties for server |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6932 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error in local name |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6933 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CMX: error during attach |
| Long Text: | Internal error in CMX. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6950 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | No error |
| Long Text: | SQL*Net AppleTalk error codes base. This is not an error. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6951 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Operating system call error |
| Long Text: | AppleTalk API received error in VMS system service. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6952 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Remote end of the communication issued a forward-reset packet. |
| Long Text: | Peer program may have aborted. |
| Repair Text: | From Oracle doc: Investigate network problems and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6953 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Not enough virtual memory |
| Long Text: | Not enough memory available. |
| Repair Text: | From Oracle doc: Check VMS process quotas and/or SYSGEN parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6954 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Illegal file name |
| Long Text: | Erroneous file name. |
| Repair Text: | From Oracle doc: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6955 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Number of database servers exceed limit |
| Long Text: | Too many database connections. |
| Repair Text: | From Oracle doc: Check ATKSRV_MAXCON parameter in configuration file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6956 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Failed to get local host name |
| Long Text: | Unable to get Appletalk host name. |
| Repair Text: | From Oracle doc: Check Appletalk configuration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6957 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No SID is currently available |
| Long Text: | Incoming SQL*Net connection specified invalid SID name. |
| Repair Text: | From Oracle doc: Specify correct SID in connect string and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6958 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Failed to access configuration file |
| Long Text: | Unable to access CONFIG.ATK. |
| Repair Text: | From Oracle doc: Check file protections. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6959 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Buffer I/O quota is too small |
| Long Text: | Buffered I/O quota exceeded. |
| Repair Text: | From Oracle doc: Increase BIOLM using AUTHORIZE utility and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6960 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Failed to access log file |
| Long Text: | SQL*Net Appletalk listener could not create log file. |
| Repair Text: | From Oracle doc: Check directory path and protections. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6961 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Insufficient privilege for attempted operation |
| Long Text: | You do not have sufficient privileges for the attempted operation. |
| Repair Text: | From Oracle doc: Check process privileges and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6970 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: remote host is unknown |
| Long Text: | Host name specified in the login (connect string) is unknown. |
| Repair Text: | From Oracle doc: Check spelling; make sure name is in the X.25 HOST file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6971 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: error while receiving data |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6972 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: error while sending data |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6973 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: invalid buffer size |
| Long Text: | The buffer size specified in the login string must be between 5 and 4096. |
| Repair Text: | From Oracle doc: Re-submit with valid buffer size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6974 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: SID lookup failure |
| Long Text: | From the remote host's SQL*Net X.25 server: the database SID, specified in the login (connect) string, was not recognized. |
| Repair Text: | From Oracle doc: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net X.25 server). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6975 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: connect to host failed |
| Long Text: | Connection attempt to remote host has failed. Probably means that the SQL*Net X.25 server on the remote host is not up, or the host itself is not up. |
| Repair Text: | From Oracle doc: Start the SQL*Net X.25 server process on the remote host. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6976 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: endpoint creation failure |
| Long Text: | Process open file quota probably exceeded. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6977 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: X.25 Level 2 failure |
| Long Text: | X.25 level 2 is down. X.25 link is not working. |
| Repair Text: | From Oracle doc: Run system checks to verify functioning of X.25 software. Contact your hardware vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6978 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: Too many callback tries |
| Long Text: | Call back address probably same as called address. |
| Repair Text: | From Oracle doc: Verify that the callback address and called address are different. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-6979 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | X.25 Driver: server cannot start oracle |
| Long Text: | The remote X.25 server was unable to start an Oracle process on behalf of the client. |
| Repair Text: | From Oracle doc: Make sure permissions on the remote Oracle program are correctly set. Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsid: oracle_sid not set. |
| Long Text: | The environment variable $(ORACLE_SID) is not set. |
| Repair Text: | From Oracle doc: Set ORACLE_SID environment variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slhom: oracle_home variable not set in environment. |
| Long Text: | $(ORACLE_HOME) environment variable not set. |
| Repair Text: | From Oracle doc: Set ORACLE_HOME. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sltln: invalid parameter to sltln. |
| Long Text: | The SLTLN name translation routine was called with invalid arguments. The input, or output stings were either NULL or 0 length. |
| Repair Text: | From Oracle doc: Probable internal Oracle error. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sltln: attempt to translate a long environment variable. |
| Long Text: | A string was passed to SLTLN containing a long environment variable. SLTLN accepts environment names of 30 or less characters. |
| Repair Text: | From Oracle doc: Shorten environment variable name to less than 30 characters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sltln: name translation failed due to lack of output buffer space. |
| Long Text: | The SLTLN routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. |
| Repair Text: | From Oracle doc: Possible internal error. Check output buffer length stored in sercose[0]. Path names are limited to 255 characters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgtd: time error, unable to obtain time. |
| Long Text: | Time() system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgtd: gettimeofday error, unable to obtain time. |
| Long Text: | GETTIMEOFDAY() system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sigpidu: process ID %s overflows internal buffer. |
| Long Text: | The SIGPIDU routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfwfb: failed to flush dirty buffers to disk. |
| Long Text: | The FSYNC system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfofi: file size limit was exceeded. |
| Long Text: | The size of the file to be opened exceeded the operating system limit imposed on this process. |
| Repair Text: | From Oracle doc: Run OSH to increase the file size limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slcpu: getrusage error, unable to get cpu time. |
| Long Text: | GETRUSAGE system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgcs: gettimeofday error, unable to get wall clock. |
| Long Text: | GETTIMEOFDAY system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned in the operating system reference manual. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slcpu: times error, unable to get cpu time. |
| Long Text: | times system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgcs: times error, unable to get wall clock. |
| Long Text: | Times system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned in the operating system reference manual. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgunm: uname error, unable to get system information. |
| Long Text: | UNAME system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned in the operating system reference manual. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: getrusage error. |
| Long Text: | GETRUSAGE system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Look for information in the operating system reference manual. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slghst: gethostname error, unable to get name of current host. |
| Long Text: | GETHOSTNAME system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned in the operating system reference manual. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sltln: environment variable cannot be evaluated. |
| Long Text: | GETENV call returned a null pointer. |
| Repair Text: | From Oracle doc: Set the environment variable and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slkhst: could not perform host operation |
| Long Text: | UNIX system() call failed. |
| Repair Text: | From Oracle doc: Examine system error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: unable to allocate spooler argument buffer. |
| Long Text: | MALLOC failed to allocate space to hold spooler arguments. |
| Repair Text: | From Oracle doc: Check additional information returned in the operating system reference manual. The process may have run out of heap space. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7220 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: wait error. |
| Long Text: | Wait returned an error, when waiting for spool job to complete. Possible spooler program error. |
| Repair Text: | From Oracle doc: Check additional information returned. Refer to the operating system reference manual. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7221 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: exec error, unable to start spooler program. |
| Long Text: | Exec failed when starting line printer spooler command. Likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set. |
| Repair Text: | From Oracle doc: Verify default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7222 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: line printer spooler command exited with an error. |
| Long Text: | The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file. |
| Repair Text: | From Oracle doc: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit value returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7223 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: fork error, unable to spawn spool process. |
| Long Text: | Fork system call failed to create additional process. Probable resource limit reached. |
| Repair Text: | From Oracle doc: Check additional information returned. Retry operation. Contact system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7224 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfnfy: failed to obtain file size limit; errno = %s. |
| Long Text: | The ULIMIT system call returned an error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7225 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sldext: translation error, unable to expand file name. |
| Long Text: | Additional information returned is error returned from SLTLN. |
| Repair Text: | From Oracle doc: Check additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7226 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rtneco: unable to get terminal mode. |
| Long Text: | The IOCTL call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information for errno. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7227 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rtneco: unable to set noecho mode. |
| Long Text: | The IOCTL call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information for errno. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7228 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rtecho: unable to restore terminal to echo mode. |
| Long Text: | The IOCTL call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information for errno. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7229 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slcpuc: error in getting number of CPUs. |
| Long Text: | Error in MPCNTL system call. |
| Repair Text: | From Oracle doc: Examine errno. Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcr: fopen error, unable to open error file. |
| Long Text: | FOPEN failed to open file. |
| Repair Text: | From Oracle doc: Try to determine which file was not opened. Check that file exists and is accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcc: invalid file handle, seals do not match. |
| Long Text: | Function was called with an invalid argument. The file handle used was not obtained be SLEMCR. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcc: fclose error. |
| Long Text: | An error was encountered when closing the file. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcw: invalid file handle, seals do not match. |
| Long Text: | Function was called with an invalid file handle. File handle was not obtained by SLEMCR. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcw: fseek error. |
| Long Text: | Unable to seek to desired position in file. Possible operating system error. Possible internal error. |
| Repair Text: | From Oracle doc: Verify that error message file is intact. Try to regenerate error message file. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcw: fwrite error. |
| Long Text: | Unable to write item to file. Possible operating system error. Possible permissions problem. |
| Repair Text: | From Oracle doc: Retry operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7236 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemop: open error. |
| Long Text: | Unable to open error file. Possible permissions problem. |
| Repair Text: | From Oracle doc: Verify permission on error message file. Check additional information for errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7237 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcl: invalid file handle, seals do not match. |
| Long Text: | Function was called with an invalid file handle. Handle was not obtained by previous call to SLEMOP. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7238 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcl: close error. |
| Long Text: | Unable to close file. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact system administrator. Check additional information for errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7239 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemrd: invalid file handle, seals do not match. |
| Long Text: | Function was called with invalid file handle. Handle was not obtained by call to SLEMOP. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7240 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemrd: seek error. |
| Long Text: | Unable to seek to desired position in file. Possible operating system error. |
| Repair Text: | From Oracle doc: Check that error file is still intact. Verify space on device. Contact system administrator. Check additional information for errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7241 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemrd: read error. |
| Long Text: | Unable to read file. Possible operating system error. |
| Repair Text: | From Oracle doc: Verify that error file is intact. Regenerate error message file. Contact Oracle Customer Support. Check additional information for errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7242 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slembfn: translation error, unable to translate error file name. |
| Long Text: | Additional information indicates error returned from SLTLN. |
| Repair Text: | From Oracle doc: Check additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7243 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftget: supplied buffer not big enough to hold entire line. |
| Long Text: | The FGETS call read only part of the line because the supplied buffer was not big enough. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. Additional information indicates how big the supplied buffer was. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7244 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssfccf: create file failed, file size limit reached. |
| Long Text: | An attempt was made to create a file that exceeds the process's file size limit. |
| Repair Text: | From Oracle doc: Run OSH to raise the file size limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7245 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfccf: unable to lseek and write the last block. |
| Long Text: | An attempt was made to move and write to a bad device address. |
| Repair Text: | From Oracle doc: Check errno. Possible lack of space on device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7246 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfofi: open error, unable to open database file. |
| Long Text: | SFOFI returns an error. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7247 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfrfb: read error, unable to read requested block from database file. |
| Long Text: | SFRFB returns an error. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7248 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfwfb: write error, unable to write database block. |
| Long Text: | SFWFB returns an error. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7249 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: open error, unable to open /proc/pid. |
| Long Text: | OPEN() returns an error. |
| Repair Text: | From Oracle doc: Check that /proc has the right permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spcre: semget error, unable to get first semaphore set. |
| Long Text: | An error occurred when trying to get first semaphore set. |
| Repair Text: | From Oracle doc: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spcre: semget error, could not allocate any semaphores. |
| Long Text: | SEMGET failed to even allocate a single semaphore. Either they are all in use or the system is not configured to have any semaphores. |
| Repair Text: | From Oracle doc: Check to see if all semaphores are in use. Check to see if system is configured to have semaphores. Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7252 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spcre: semget error, could not allocate semaphores. |
| Long Text: | SEMGET system call returned an error. Possible resource limit problem. |
| Repair Text: | From Oracle doc: Check errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using IPCRM. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7253 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdes: semctl error, unable to destroy semaphore set. |
| Long Text: | SEMCTL system call returned an error. |
| Repair Text: | From Oracle doc: Check semaphore sets. May require manual cleanup. Check additional information returned. Consult operating system reference manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7254 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: translation error while expanding ?/bin/oracle. |
| Long Text: | An error occurred while translating the name of the Oracle executable. |
| Repair Text: | From Oracle doc: Check sercose[0] for error returned from SLTLN. Perhaps $(ORACLE_HOME) is not set correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7255 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spini: cannot set up signal handler. |
| Long Text: | System failed to set up signal handler. |
| Repair Text: | From Oracle doc: Check errno and sercose[0] for the signal number that failed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7256 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sptrap: cannot set up signal handler to catch exceptions. |
| Long Text: | System failed to set up signal handler to catch exceptions. |
| Repair Text: | From Oracle doc: Check errno and sercose[0] for the signal number that failed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7257 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: translation error expanding program name. |
| Long Text: | Error occurred when expanding program name ora_PNAME_@. The result of this translation is put in argv[0] of Oracle process. |
| Repair Text: | From Oracle doc: Check error returned by SLTLN returned in sercose[0]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7258 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: fork error, unable to create process. |
| Long Text: | An error occurred when creating a new process. |
| Repair Text: | From Oracle doc: Check errno. Perhaps a system limit on the number of processes has been exceeded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7259 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: exec error, detached process failed in startup. |
| Long Text: | An Oracle detached process died shortly after startup. Wait() indicated that a child process terminated. |
| Repair Text: | From Oracle doc: Check ?/dbs directory for trace or core files. Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: wait error. |
| Long Text: | Wait system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdde: kill error, unable to send signal to process. |
| Long Text: | Kill system call returned an error. Possibly an attempt to destroy an already gone process. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sptpa: sptpa called with invalid process id. |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sptpa: kill error. |
| Long Text: | Kill system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check errno. Additional information indicates the process ID tested. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7264 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: semop error, unable to decrement semaphore. |
| Long Text: | SEMOP system call returned an error. Semaphore set may not exist. |
| Repair Text: | From Oracle doc: Check errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a SHUTDOWN ABORT was done while this process was running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppst: semop error, unable to increment semaphore. |
| Long Text: | SEMOP system call returned an error. Semaphore set may not exist. |
| Repair Text: | From Oracle doc: Check errno. Semaphore ID is returned in sercose[0]. Check semaphore set existence. A possible cause for this error is that a SHUTDOWN ABORT was done while this process was running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppst: invalid process number passed to sppst. |
| Long Text: | Function was passed an invalid Oracle process ID. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7267 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: invalid process number. |
| Long Text: | Function was passed an invalid Oracle process ID. This is an internal error. |
| Repair Text: | From Oracle doc: Additional information indicates the invalid process ID. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7268 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szguns: getpwuid error. |
| Long Text: | GETPWUID() could not find an entry in the passwd file for a user. |
| Repair Text: | From Oracle doc: Add an entry for the user in the passwd file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7269 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: detached process died after exec. |
| Long Text: | Detached process successfully executed, but died shortly thereafter. Additional information indicates exit code, and termination status. |
| Repair Text: | From Oracle doc: Check termination code for information as to why process exited. Check for core dump or trace file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spalck: setitimer error, unable to set interval timer. |
| Long Text: | An error occurred while trying to set an interval timer. Probable porting problem. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: invalid oracle process number. |
| Long Text: | Function was called with an invalid Oracle process number (0). |
| Repair Text: | From Oracle doc: Internal Oracle error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7272 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: invalid semaphore set id. |
| Long Text: | Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and Oracle process number. This is an internal error. |
| Repair Text: | From Oracle doc: Check semaphore set index. Check Oracle process number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7273 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppst: invalid semaphore id. |
| Long Text: | Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index, and Oracle process number. This is an internal error. |
| Repair Text: | From Oracle doc: Check semaphore set index. Check Oracle process number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7274 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: access error, access to oracle denied. |
| Long Text: | Unable to access Oracle program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable. |
| Repair Text: | From Oracle doc: Check errno returned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7275 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to send signal to process |
| Long Text: | The kill system call returned an error. Possibly an attempt to signal a process which does not exist. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no dba group in /etc/group. |
| Long Text: | A group has not been set up for dba users. |
| Repair Text: | From Oracle doc: Contact system administrator. Set up dba group in /ETC/GROUP. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdde: illegal pid passed as argument. |
| Long Text: | A 0 PID was passed to SPDDE. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | splon: ops$username exceeds buffer length. |
| Long Text: | SPLON constructed an OPS$USERNAME logon which exceeded the allocated buffer space. |
| Repair Text: | From Oracle doc: Use a shorter UNIX username, or use an Oracle username. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7279 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spcre: semget error, unable to get first semaphore set. |
| Long Text: | An error occurred when trying to get first semaphore set. |
| Repair Text: | From Oracle doc: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7280 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: unable to get process information. |
| Long Text: | The IOCTL call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information for errno. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: times error, unable to get cpu time. |
| Long Text: | Times system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7282 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprd: %s overflow. |
| Long Text: | The internal buffer is not big enough to hold the archive control string. |
| Repair Text: | From Oracle doc: Internal restriction. Try a shorter archive control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7283 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprd: invalid volume size for archive destination. |
| Long Text: | An invalid volume size was specified. |
| Repair Text: | From Oracle doc: Specify a valid volume size in archive control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7284 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprd: volume size specification not terminated properly. |
| Long Text: | Some non-numeric text follows the volume size specification. |
| Repair Text: | From Oracle doc: Enter a correct archive control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7285 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprd: volume size should not be specified for a disk file. |
| Long Text: | Volume size was specified for a disk file. |
| Repair Text: | From Oracle doc: If you are archiving to a disk file, do not specify its volume size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7286 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksagdi: cannot obtain device information. |
| Long Text: | STAT on the log archiving device failed. |
| Repair Text: | From Oracle doc: Check the returned OSD error for the reason of failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7287 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksagdi: unsupported device for log archiving. |
| Long Text: | Log archiving to this device is unsupported. |
| Repair Text: | From Oracle doc: Try log archiving to a supported device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksagdi: specified directory for archiving does not exist. |
| Long Text: | The specified path name is not a directory. |
| Repair Text: | From Oracle doc: Verify that the archive destination directory exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ksmcsg: illegal database buffer size. |
| Long Text: | The database buffer size must be a multiple of the database block size, and less than the maximum block size. |
| Repair Text: | From Oracle doc: Verify that the DB_BLOCK_SIZE parameter is correct in INIT.ORA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ksmcsg: illegal redo buffer size. |
| Long Text: | The redo buffer size must be a multiple of machine block size. |
| Repair Text: | From Oracle doc: Verify that the LOG_BUFFER INIT.ORA parameter is correctly set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ksmcsg: illegal database buffer size. |
| Long Text: | The database buffer size must be a multiple of the extended cache mapping size for indirect data buffers to be used. |
| Repair Text: | From Oracle doc: Verify that the DB_BLOCK_SIZE parameter is correct in INIT.ORA, or disable the USE_INDIRECT_DATA_BUFFERS parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7324 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpall: malloc error while allocating pga. |
| Long Text: | MALLOC library routine returned an error. |
| Repair Text: | From Oracle doc: Check errno. Possibly out of swap space. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7327 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpdal: attempt to destroy pga when it was not mapped. |
| Long Text: | SMPDAL was called when the PGA had not been previously created. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7339 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spcre: maximum number of semaphore sets exceeded. |
| Long Text: | The internal buffer is not big enough to hold the number of semaphore set identifiers requested. |
| Repair Text: | From Oracle doc: Reconfigure operating system to have more semaphores per set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The datafile name must not contain the %s '..'. |
| Long Text: | The specified datafile name contains '..'. |
| Repair Text: | From Oracle doc: Correct the datafile name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7390 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftopn: translate error, unable to translate file name. |
| Long Text: | An error occurred while expanding the file name to open. Additional information returns error generated in translation routine. |
| Repair Text: | From Oracle doc: Look up additional error code for further information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7391 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftopn: fopen error, unable to open text file. |
| Long Text: | FOPEN library routine returned an error. |
| Repair Text: | From Oracle doc: Verify existence and permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7392 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftcls: fclose error, unable to close text file. |
| Long Text: | FCLOSE library routine returned an error. |
| Repair Text: | From Oracle doc: Possible internal Oracle error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemtr: translated name for the message file is too long. |
| Long Text: | The name for the message file overflows internal buffer. |
| Repair Text: | From Oracle doc: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sptrap: cannot restore user exception handlers. |
| Long Text: | The system failed to restore user exception handlers. |
| Repair Text: | From Oracle doc: Check errno and sercose[0] for the signal number that failed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sprst: cannot restore user signal handler. |
| Long Text: | The system failed to restore user signal handlers. |
| Repair Text: | From Oracle doc: Check errno and sercose[0] for the signal number that failed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfanfy: db_writers parameter not valid. |
| Long Text: | The DB_WRITERS parameter in INIT.ORA exceeds the system-dependent maximum or is less than 0. |
| Repair Text: | From Oracle doc: Change the DB_WRITERS parameter in INIT.ORA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfareq: Timeout occurred waiting for request to complete. |
| Long Text: | The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running. |
| Repair Text: | From Oracle doc: Check all database writer trace files. Shut down the database and try to warm start. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slbtpd: invalid number. |
| Long Text: | An impossible request for binary to decimal conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slbtpd: invalid exponent. |
| Long Text: | An impossible request for binary to decimal conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slbtpd: overflow while converting to packed decimal. |
| Long Text: | An impossible request for binary to decimal conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7409 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slpdtb: invalid packed decimal nibble. |
| Long Text: | An impossible request for decimal to binary conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7410 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slpdtb: number too large for supplied buffer. |
| Long Text: | An impossible request for decimal to binary conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7411 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgfn: full path name too big for supplied buffer. |
| Long Text: | The supplied buffer is not big enough to hold the full path name. |
| Repair Text: | From Oracle doc: The construction of the full path name cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7412 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfaslv: Error getting entry in asynchronous write array. |
| Long Text: | One of the database writer processes could not locate its entry in the SGA. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7415 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slpath: allocation of memory buffer failed. |
| Long Text: | MALLOC() failed to allocate buffer for storing ORACLE_PATH. |
| Repair Text: | From Oracle doc: System has run out of heap space. Additional information indicates errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7416 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slpath: pathname construction failed; lack of output buffer space. |
| Long Text: | The SLPATH routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This may be an internal error. |
| Repair Text: | From Oracle doc: Check output buffer length stored in sercose[0] and constructed path name length in sercose[1]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7417 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfareq: One or more database writers not active. |
| Long Text: | One or more of the database writer processes is no longer running. |
| Repair Text: | From Oracle doc: Check the trace files for the database writers. Shut down the database and try to warm start. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7418 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfareq: Database writer got error in timing function. |
| Long Text: | An error occurred when the database writer called the system timing function. |
| Repair Text: | From Oracle doc: Check the database writer trace file. Shut down the database and try to warm start. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7419 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfareq: Database writer got error in timing function. |
| Long Text: | An error occurred when the database writer called the system timing function. |
| Repair Text: | From Oracle doc: Check the database writer trace file. Shut down the database and try to warm start. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7425 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sdpri: error %s in translating dump file location. |
| Long Text: | An Oracle error occurred when translating the location of the dump file. |
| Repair Text: | From Oracle doc: Check the Oracle error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7426 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spstp: cannot obtain the location of dbs directory. |
| Long Text: | An Oracle error occurred when translating the location of the DBS directory. |
| Repair Text: | From Oracle doc: Check additional information for the error returned from SLTLN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7427 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spstp: cannot change directory to dbs. |
| Long Text: | CHDIR system call returned an error. Possible permission problems. |
| Repair Text: | From Oracle doc: Check additional information for the operating system error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fork failed |
| Long Text: | The server process was unable to fork a child process. |
| Repair Text: | From Oracle doc: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to perform nested sleep |
| Long Text: | An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability. |
| Repair Text: | From Oracle doc: Try the SLEEP command when the process is not sleeping. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | WMON process terminated with error |
| Long Text: | The wakeup monitor process died. |
| Repair Text: | From Oracle doc: Warm start instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function address must be aligned on %s byte boundary |
| Long Text: | An improperly aligned function address was specified. |
| Repair Text: | From Oracle doc: Use a properly aligned function address. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7442 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function address must be in the range %s to %s |
| Long Text: | An invalid function address was specified. |
| Repair Text: | From Oracle doc: Use a valid function address. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function %s not found |
| Long Text: | An invalid function name was specified. |
| Repair Text: | From Oracle doc: Use a valid function name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function address %s is not readable |
| Long Text: | An invalid function name/address was specified. |
| Repair Text: | From Oracle doc: Use a valid function name/address. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7445 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s] |
| Long Text: | An operating system exception occurred which should result in the creation of a core file. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sdnfy: bad value '%s' for parameter %s. |
| Long Text: | The directory specified as the value for the stated parameter could not be used. |
| Repair Text: | From Oracle doc: Make sure the directory you have specified is a valid directory/file specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7447 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssarena: usinit failed. |
| Long Text: | Oracle failed to create a shared arena file. |
| Repair Text: | From Oracle doc: Use SERCERRNO field to determine cause of failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7448 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssarena: maximum number of shared arenas exceeded. |
| Long Text: | Oracle attempted to create more shared arena files than permitted. |
| Repair Text: | From Oracle doc: Raise the value for MAX_ARENA in INIT.ORA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sc: usnewlock failed. |
| Long Text: | Oracle failed to acquire a shared arena lock. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO to determine the cause of failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slskstat: unable to obtain load information. |
| Long Text: | KSTAT library returned an error. Possible operating system failure. |
| Repair Text: | From Oracle doc: Check result code in sercose[0] for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified resource manager plan does not exist in the data dictionary |
| Long Text: | User tried to load a resource manager plan that does not exist. |
| Repair Text: | From Oracle doc: Use a resource manager plan that exists in the data dictionary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | requested resource manager plan schema does not contain OTHER_GROUPS |
| Long Text: | User tried to load a resource manager plan schema that does not contain the OTHER_GROUPS group. |
| Repair Text: | From Oracle doc: Use a resource manager plan schema that contains the OTHER_GROUPS group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7468 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: mset wrror, unable to set semaphore. |
| Long Text: | The MSET routine returned an error. Semaphore may not exist. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Semaphore number returned in sercose[0]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7469 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppst: mclear error, unable to clear semaphore. |
| Long Text: | The MCLEAR routine returned an error. Semaphore may not exist. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Semaphore number returned in sercose[0]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7470 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snclget: cannot get cluster number. |
| Long Text: | The CLUSTER_STATUS system call failed to get status information for the current cluster. |
| Repair Text: | From Oracle doc: Check result code in sercose[0]. Possible operating system failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7471 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snclrd: name translation error of sgadef.dbf file name. |
| Long Text: | Unable to expand out ?/dbs/sgadef@.dbf file name. |
| Repair Text: | From Oracle doc: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check error number returned from SLTLN in sercose[0]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7472 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snclrd: open error when opening sgadef.dbf file. |
| Long Text: | Open failed when opening the file ?/dbs/sgadef@.dbf. |
| Repair Text: | From Oracle doc: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7473 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snclrd: read error when trying to read sgadef.dbf file. |
| Long Text: | Read had an error when reading SGADEF.DBF file. |
| Repair Text: | From Oracle doc: Check errno. Verify file exists, and is correct size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7474 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snclrd: close error, unable to close sgadef.dbf file. |
| Long Text: | An error occurred in close, while closing the file ?/dbs/sgadef@.dbf. |
| Repair Text: | From Oracle doc: Check errno. Possible operating system error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7475 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: cannot get vm statistics. |
| Long Text: | The VM_STATISTICS system call failed to get virtual memory statistics. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible operating system failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7476 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: cannot get mapped memory statistics. |
| Long Text: | The VM_MAPMEM system call failed to get mapped memory statistics. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible operating system failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7477 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcmn: lock manager not initialized. |
| Long Text: | Lock manager must be initialized before converting locks. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7478 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcmn: cannot get lock status. |
| Long Text: | LM_STAT_LOCK failed. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7479 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcmn: cannot open or convert lock. |
| Long Text: | LM_OPEN or LM_OPEN_CONVERT failed. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7480 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snchmod: cannot change permissions on ?/dbs/sgalm.dbf. |
| Long Text: | When creating an instance, SNLMINI could not change the permissions on ?/dbs/sgalm.dbf. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7481 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snlmatt: cannot attach to lock manager instance. |
| Long Text: | LM_ATTACH failed to attach to Lock Manager instance. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7482 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snlmini: cannot create lock manager instance. |
| Long Text: | LM_CREATE failed to create Lock Manager instance. |
| Repair Text: | From Oracle doc: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7483 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snlkget: cannot convert(get) lock. |
| Long Text: | LM_CONVERT failed to convert(get) lock. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7484 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snlkput: cannot convert(put) lock. |
| Long Text: | LM_CONVERT failed to put lock value. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7485 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scg_get_inst: cannot open instance number lock. |
| Long Text: | LM_OPEN failed. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7486 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scg_get_inst: cannot convert(get) instance number lock. |
| Long Text: | LM_CONVERT failed to get lock value. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7487 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scg_init_lm: cannot create lock manager instance. |
| Long Text: | LM_CREATE failed. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7488 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgrcl: lock manager not initialized. |
| Long Text: | Lock manager must be initialized before releasing locks. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7489 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgrcl: cannot get lock status. |
| Long Text: | LM_STAT_LOCK failed during lock release/cancel. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7490 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgrcl: cannot convert lock. |
| Long Text: | LM_CONVERT failed during lock release/cancel. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7491 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgrcl: cannot cancel lock request. |
| Long Text: | LM_CANCEL failed during lock release/cancel. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7492 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgrcl: cannot close lock. |
| Long Text: | LM_CLOSE failed during lock release/cancel. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7493 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgrcl: lock manager error. |
| Long Text: | An error was encountered releasing the lock. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7494 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcm: unexpected error. |
| Long Text: | Unknown or unexpected error code. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7495 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: lm_wait failed. |
| Long Text: | LM_WAIT failed. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7496 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppst: lm_post failed. |
| Long Text: | LM_POST failed. |
| Repair Text: | From Oracle doc: Check result code in SERCERRNO. Possible Lock Manager failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7497 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sdpri: cannot create trace file '%s'; errno = %s. |
| Long Text: | The trace file cannot be created for writing. |
| Repair Text: | From Oracle doc: Check if the dump directory exists and whether it is writable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7498 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spstp: Unable to open /dev/resched. |
| Long Text: | The rescheduling driver /dev/resched is not found or is not working properly. |
| Repair Text: | From Oracle doc: Check installation of the Oracle rescheduling driver in the AIX kernel. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7499 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spglk: Cannot reschedule. |
| Long Text: | The rescheduling driver /dev/resched is not open. This is an internal error and should not occur. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scglaa: $cantim unexpected return |
| Long Text: | VMS system service $CANTIM returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgtoa: $deq unexpected return |
| Long Text: | VMS system service $DEQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcmn: $enq unexpected return |
| Long Text: | VMS system service $ENQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcmn: $setimr unexpected return |
| Long Text: | VMS system service $SETIMR returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcmn: $hiber unexpected return |
| Long Text: | VMS system service $HIBER returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scggt: $enq parent lock unexpected return |
| Long Text: | VMS system service $ENQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgrl: $deq unexpected return on lockid %s |
| Long Text: | VMS system service $DEQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcm: unexpected lock status condition |
| Long Text: | A global locking system service returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message (if any) and refer to VMS documentation, or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgfal: $deq all unexpected return |
| Long Text: | VMS system service $DEQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgfal: $deq parent lock unexpected return |
| Long Text: | VMS system service $DEQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgbrm: $getlki unexpected return on lockid %s |
| Long Text: | VMS system service $GETLKI returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sscggtl: $enq unexpected return for master termination lock |
| Long Text: | VMS system service $ENQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sscggtl: $enq unexpected return for client termination lock |
| Long Text: | VMS system service $ENQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sscgctl: $deq unexpected return on cancel of term. lock |
| Long Text: | VMS system service $DEQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcan: $deq unexpected return while canceling lock |
| Long Text: | VMS system service $DEQ returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scginq: $getlki unexpected return on lockid %s |
| Long Text: | VMS system service $GETLKI returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7548 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftopn: Maximum number of files already open |
| Long Text: | Too many test files open. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7549 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftopn: $OPEN failure |
| Long Text: | VMS system service $OPEN failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7550 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftopn: $CONNECT failure |
| Long Text: | VMS system service $OPEN failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftcls: $CLOSE failure |
| Long Text: | VMS system service $CLOSE failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftget: $GET failure |
| Long Text: | VMS system service $GET failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7561 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szprv: $IDTOASC failure |
| Long Text: | VMS system service $IDTOASC failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7562 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sldext: extension must be 3 characters |
| Long Text: | An extension was found but it is of improper length. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7563 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sldext: $PARSE failure |
| Long Text: | VMS system service $PARSE failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7564 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sldext: wildcard in filename or extension |
| Long Text: | A wildcard was used in the file name. |
| Repair Text: | From Oracle doc: Re-enter the file name completely. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7565 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sldext: $SEARCH failure |
| Long Text: | VMS system service $SEARCH failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7568 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: $OPEN failure |
| Long Text: | VMS system service $OPEN failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7569 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: $CLOSE failure |
| Long Text: | VMS system service $CLOSE failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7570 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrfc: $IDTOASC failure |
| Long Text: | VMS system service $IDTOASC failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7571 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrfc: $FIND_HELD failure |
| Long Text: | VMS system service $FIND_HELD failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7572 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrfc: insufficient rolename buffer space |
| Long Text: | An OS role name was too long. |
| Repair Text: | From Oracle doc: Re-define the role name to be of correct length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7573 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slkhst: could not perform host operation |
| Long Text: | VMS system service LIB$SPAWN failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7574 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrfc: $GETUAI failure |
| Long Text: | VMS system service $GETUAI failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7576 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspexst: $GETJPIW failure on process ID %s |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7577 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no such user in authorization file |
| Long Text: | An attempt was made to set an INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS account (either ORA_sid_DBA or ORA_sid_OPER) has not been created yet. |
| Repair Text: | From Oracle doc: Add a VMS account for ORA_sid_DBA and/or ORA_sid_OPER before trying to set a password for them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7578 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szprv: $FIND_HELD failure |
| Long Text: | VMS system service $FIND_HELD failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7579 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spini: $DCLEXH failure |
| Long Text: | VMS system service $PARSE failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7580 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spstp: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7581 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spstp: cannot derive SID from unexpected process name |
| Long Text: | A background process did not have name of correct form. |
| Repair Text: | From Oracle doc: If the job name was changed, restore it. Otherwise, this is an internal error; report it to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7582 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spstp: ORA_SID has illegal value |
| Long Text: | The ORA_SID must exist and be less than 6 characters. |
| Repair Text: | From Oracle doc: Consult the VMS Installation guide for information on setting the SID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7584 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: invalid value for ORA_sid_(proc_)PQL$_item |
| Long Text: | A logical name used to set a detached process quota value has an invalid value (probably non-numeric). |
| Repair Text: | From Oracle doc: Examine the values of these logical names, correct the one in error, and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7585 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: $PARSE failure |
| Long Text: | VMS system service $PARSE failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7586 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: $SEARCH failure |
| Long Text: | VMS system service $SEARCH failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7587 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: $CREPRC failure |
| Long Text: | VMS system service $CREPRC failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7588 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: $GETJPIW get image name failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7589 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdde: system ID not set |
| Long Text: | The logical name ORA_SID does not translate to a valid value. |
| Repair Text: | From Oracle doc: Check the value of ORA_SID in the process that gets the error, and correct the installation or command procedures that caused ORA_SID to be set incorrectly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7590 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdde: $DELPRC failure |
| Long Text: | VMS system service $DELPRC failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7591 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdde: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7592 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspgprv: Error obtaining required privileges |
| Long Text: | While obtaining needed privileges, an error was returned from SYS$SETPRV. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7593 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssprprv: Error release privileges |
| Long Text: | While releasing privileges, an error was returned from SYS$SETPRV. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7594 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spiip: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7595 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppid: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7596 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sptpa: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7597 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spguns: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7598 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: $SETIMR failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7599 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: $SCHDWK failure |
| Long Text: | VMS system service $SCHDWK failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slkmnm: $GETSYIW failure |
| Long Text: | VMS system service $GETSYIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spguno: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7602 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spgto: $GETJPIW failure |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7605 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szprv: $ASCTOID failure |
| Long Text: | VMS system service $ASCTOID failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szprv: $CHKPRO failure |
| Long Text: | VMS system service $CHKPRO failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7607 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szaud: $SNDOPR failure |
| Long Text: | VMS system service $SNDOPR failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7608 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szprv: $GETUAI failure |
| Long Text: | VMS system service $GETUAI failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7609 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szprv: $HASH_PASSWORD failure |
| Long Text: | VMS system service $HASH_PASSWORD failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7610 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $GETJPIW failed in retrieving the user's MAC priviledges |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7612 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $GETUAI failed in retrieving the user's clearance level |
| Long Text: | VMS system service $GETUAI failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7613 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $GETJPIW failed in retrieving the user's process label |
| Long Text: | VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7614 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $CHANGE_CLASS failed in retrieving the user's process label |
| Long Text: | VMS system service $CHANGE_CLASS failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to SEVMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7615 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $CHANGE_CLASS failed in retrieving the specified file label |
| Long Text: | VMS system service $CHANGE_CLASSS failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to SEVMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7616 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $CHANGE_CLASS failed in retrieving the specified device label |
| Long Text: | VMS system service $CHANGE_CLASS failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to SEVMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7617 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $FORMAT_CLASS failed translating the binary label to a %s |
| Long Text: | VMS system service $FORMAT_CLASS failed because the given binary classification was not valid. |
| Repair Text: | From Oracle doc: Examine system error message and refer to SEVMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7618 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $IDTOASC failed translating a secrecy level |
| Long Text: | VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy level. |
| Repair Text: | From Oracle doc: Define the entry in the rights database which the binary label you specified references. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7619 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $IDTOASC failed translating an integrity level |
| Long Text: | VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity level. |
| Repair Text: | From Oracle doc: Define the entry in the rights database which the binary label you specified references. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7620 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: illegal database block size |
| Long Text: | An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical i/o data size. |
| Repair Text: | From Oracle doc: Change DB_BLOCK_SIZE in the parameter file to conform to these limits. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7621 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: illegal redo block size |
| Long Text: | An illegal redo log buffer size was specified in the parameter file. It must be positive and a multiple of 512. |
| Repair Text: | From Oracle doc: Change LOG_BUFFER in the parameter file to conform to these limits. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7622 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: $CREATE failure |
| Long Text: | While creating the system global area (SGA) backing file, VMS system service $CREATE failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7623 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: $CRMPSC failure |
| Long Text: | While creating the system global area (SGA), VMS system service $CRMPSC failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7624 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdes: $DGBLSC failure |
| Long Text: | While deleting the system global area (SGA), VMS system service $DGBLSC failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7625 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: $MGBLSC failure |
| Long Text: | While mapping the system global area (SGA) during logon, VMS system service $MGBLSC failed. The usual reason is that Oracle has not been started up. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. Start Oracle if it is not already started. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7626 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: sga already mapped |
| Long Text: | An attempt to map the SGA during logon failed because it was already mapped. This is an internal error. |
| Repair Text: | From Oracle doc: Exit your program and try again, and report this to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7627 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsfre: $CRETVA failure |
| Long Text: | While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7628 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsfre: sga not mapped |
| Long Text: | An attempt to unmap the SGA during logoff failed because it was not mapped. This is an internal error. |
| Repair Text: | From Oracle doc: Exit your program and try again, and report this to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7629 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpall: $EXPREG failure |
| Long Text: | While extending the program global area (PGA), VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7630 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpdal: $DELTVA failure |
| Long Text: | While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7631 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smcacx: $EXPREG failure |
| Long Text: | While creating or extending a context area, VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7632 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsrcx: $DELTVA failure |
| Long Text: | While deleting a context area, VMS system service $DELTVA failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7633 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdbp: illegal protection value |
| Long Text: | The buffer debug function was called with an illegal value. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7634 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdbp: $CRETVA failure |
| Long Text: | While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7635 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdbp: $SETPRT failure |
| Long Text: | While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7636 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdbp: $MGBLSC failure |
| Long Text: | While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7637 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdbp: buffer protect option not specified when sga created |
| Long Text: | An attempt was made to change the buffer protect mode when the SGA was not created with buffer protect debug option. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7638 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: SGA pad area not large enough for created SGA |
| Long Text: | An attempt was made to map an SGA with software in which the SGA pad area is not large enough. |
| Repair Text: | From Oracle doc: Create a smaller SGA, or relink the software with a larger pad. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7639 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: SGA pad area not large enough (%s bytes required) |
| Long Text: | An attempt was made to create an SGA with software in which the SGA pad area is not large enough. |
| Repair Text: | From Oracle doc: Create a smaller SGA, or relink the software with a larger pad. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7640 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | smsget: SGA not yet valid. Initialization in progress |
| Long Text: | An attempt was made to map to the SGA while it was being initialized. |
| Repair Text: | From Oracle doc: Wait until initialization is complete, and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7641 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: Unable to use the system pagefile for the SGA |
| Long Text: | The system global area (SGA) backing file could not be allocated using the system pagefile because the system-wide limit on global pages has been exceeded. |
| Repair Text: | From Oracle doc: Either increase the VMS system parameter GBLPAGFIL or use a disk file as the SGA backing file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7642 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smprtset: $CMKRNL failure |
| Long Text: | While attempting to set the protection of a region of memory, an error was returned from the $CMKRNL system service. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7643 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsalo: SMSVAR is invalid |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Report this error to Oracle Customer Support; provide your INIT.ORA file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7645 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sszfsl: $CHANGE_CLASS failure |
| Long Text: | While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed. |
| Repair Text: | From Oracle doc: Examine the system message and refer to SEVMS system documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7646 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sszfck: $CREATE failure |
| Long Text: | While attempting to create a file, VMS system service $CREATE failed. |
| Repair Text: | From Oracle doc: Examine the system message and refer to VMS system documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7647 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sszfck: $OPEN failure |
| Long Text: | While attempting to reopen a file, VMS system service $OPEN failed. |
| Repair Text: | From Oracle doc: Examine the system message and refer to VMS system documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7650 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sigunc: $GETJPIW failure |
| Long Text: | While attempting to get the user's terminal device name, user name, user program name, or process name during logon, VMS system service $GETJPIW failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7655 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsprom:$TRNLOG failure |
| Long Text: | While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7656 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsprom:$GETDVI failure |
| Long Text: | While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7657 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsprom:$ASSIGN failure |
| Long Text: | While prompting for a password, VMS system service $ASSIGN failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7658 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsprom:$QIOW read failure |
| Long Text: | While prompting for a password, VMS system service $QIOW failed. |
| Repair Text: | From Oracle doc: Examine the system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7665 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ssrexhd: recursive exception encountered %s %s %s %s %s %s |
| Long Text: | A VMS exception occurred while executing in the Oracle exception handler. The message includes the signal number, first and second signal arguments, and exception PC, PSL and R0. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7670 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $IDTOASC failed translating a secrecy category |
| Long Text: | VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy category. |
| Repair Text: | From Oracle doc: Define the entry in the rights database which the binary label you specified references. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7671 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $IDTOASC failed translating an integrity category |
| Long Text: | VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity category. |
| Repair Text: | From Oracle doc: Define the entry in the rights database which the binary label you specified references. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7672 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | $PARSE_CLASS failed translating the %s into a binary label |
| Long Text: | SEVMS system service $PARSE_CLASS failed because the given string did not represent a valid classification. |
| Repair Text: | From Oracle doc: Examine system error message and refer to SEVMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7680 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2os: another call to ORACLE currently executing |
| Long Text: | A call to the Oracle shared image entry point occurred from within the shared image. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7681 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2os: An error occurred while initializing Oracle |
| Long Text: | While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7682 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2os: set kernel dispatch fail err |
| Long Text: | During Oracle shared image entry, a dispatch to kernel mode failed. |
| Repair Text: | From Oracle doc: Make sure that your shared image is installed with the CMKRNL privilege, then contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7683 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2os: $SETPRV reset error |
| Long Text: | During an attempt to restore user privileges at Oracle shared image exit, VMS system service $SETPRV failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7684 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2os: supervisor stack reset error |
| Long Text: | During an attempt to restore the supervisor-mode stack at Oracle shared image exit, VMS system service $SETSTK failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7685 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sou2os: supervisor stack set error |
| Long Text: | During an attempt to set the Oracle supervisor-mode stack at Oracle shared image entry, VMS system service $SETSTK failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7700 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksarch: interrupt received |
| Long Text: | An interrupt was received while archiving the logs. |
| Repair Text: | From Oracle doc: Retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksatln: internal exception: output buffer too small |
| Long Text: | Overflow of buffer for parsing archive control text string. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unrecognized device type in archive text |
| Long Text: | Unrecognized device type in archive text. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in archive text: need '/' after device type |
| Long Text: | The archive control text in the ARCHIVE command is invalid; the device type (to indicate a file or tape) must be followed by a '/'. |
| Repair Text: | From Oracle doc: Refer to the Oracle8i Backup and Recovery Guide for the proper syntax of the text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in archive text: need ':' after device name |
| Long Text: | The archive control text in the ARCHIVE command is invalid; the device name must be followed by a ':'. |
| Repair Text: | From Oracle doc: Refer to the Oracle8i Backup and Recovery Guide for the proper syntax of the text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprs: device name buffer too small |
| Long Text: | The buffer supplied for the device name is too small. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in archive text: need disk file name |
| Long Text: | The archive control text in the ARCHIVE command is invalid; the disk file name is missing. |
| Repair Text: | From Oracle doc: Refer to the Oracle8i Backup and Recovery Guide for the proper syntax of the text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7707 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in archive text: need tape label name |
| Long Text: | The archive control text in the ARCHIVE command is invalid; the tape label name is missing. |
| Repair Text: | From Oracle doc: Refer to the Oracle8i Backup and Recovery Guide for the proper syntax of the text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprs: tape label name buffer too small |
| Long Text: | The buffer supplied for the tape label is too small. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprs: archiving to a remote host is not allowed |
| Long Text: | The user specified a remote disk for archiving via DECnet. |
| Repair Text: | From Oracle doc: Archive to a disk on the local host. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7710 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaprs: file name buffer too small |
| Long Text: | The buffer supplied for the file name is too small. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7713 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksamtd: could not mount archival device (SYS$MOUNT failure) |
| Long Text: | VMS system service SYS$MOUNT failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7715 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksadtd: could not dismount archival device (SYS$DISMNT failure) |
| Long Text: | VMS system service SYS$DISMNT failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7716 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksachk: invalid device specification for ARCHIVE |
| Long Text: | VMS system service SYS$GETDVI failed". |
| Repair Text: | From Oracle doc: Specify a valid device in ARCHIVE control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7717 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaalo: error allocating memory |
| Long Text: | VMS system service LIB$GET_VM failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7718 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksafre: error freeing memory |
| Long Text: | VMS system service LIB$FREE_VM failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7721 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcm: not enough OS resource to obtain system enqueue |
| Long Text: | A call to SYS$ENQ returned an error indicating that the operating system lacked the resources necessary to create a lock. This is caused by the messages SS$_EXENQLM or SS$_INSFMEM. |
| Repair Text: | From Oracle doc: Free up some of the required resource to allow the creation of the required lock. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7740 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemop: incorrect handle size (programming error) |
| Long Text: | Structures used for reading error message files do not match. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7741 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemop: $OPEN failure |
| Long Text: | VMS system service $OPEN failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7742 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemop: $CONNECT failure |
| Long Text: | VMS system service $CONNECT failed. |
| Repair Text: | From Oracle doc: Examine system error message and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7743 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemop: incorrect error file attributes |
| Long Text: | An error message file is of incorrect format. |
| Repair Text: | From Oracle doc: Unless an error file has been changed, report this to Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7744 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcl: invalid error message file handle |
| Long Text: | Seal in passed in handle does not match correct value. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7745 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcl: $CLOSE failure |
| Long Text: | VMS system service $CLOSE failed. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7746 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemrd: invalid error message file handle |
| Long Text: | seal in passed in handle does not match correct value. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7747 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemrd: $READ failure |
| Long Text: | VMS system service $READ failed. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7750 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcr: fopen failure |
| Long Text: | An attempt to create a message file failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7751 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcr: malloc failure |
| Long Text: | An attempt to allocate a cache for a newly-created message file failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7753 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcf: fseek before write failure |
| Long Text: | An attempt to seek before writing a message file cache element failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7754 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcf: fwrite failure |
| Long Text: | An attempt to write a message file cache element failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7755 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcf: fseek before read failure |
| Long Text: | An attempt to seek before reading a message file cache element failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7756 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcf: fread failure |
| Long Text: | An attempt to read a message file cache element failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7757 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcc: invalid handle |
| Long Text: | The seal in a passed-in handle does not match correct value. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7758 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemcw: invalid handle |
| Long Text: | The seal in a passed-in handle does not match correct value. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7759 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemtr: invalid destination |
| Long Text: | The destination string provided to the function is too short. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7760 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slemtr: $open failure |
| Long Text: | The $open service failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slbtpd: invalid number |
| Long Text: | An impossible request for binary to decimal conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slbtpd: invalid exponent |
| Long Text: | An impossible request for binary to decimal conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slbtpd: overflow while converting to packed decimal |
| Long Text: | An impossible request for binary to decimal conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slpdtb: invalid packed decimal nibble |
| Long Text: | An impossible request for decimal to binary conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slpdtb: number too large for supplied buffer |
| Long Text: | An impossible request for decimal to binary conversion was made. |
| Repair Text: | From Oracle doc: This conversion cannot be performed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7820 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspscn: SYS$CRELNM failure |
| Long Text: | An error was returned from the SYS$CRELNM function. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7821 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspsdn: SYS$DELLNM failure |
| Long Text: | An error was returned from the SYS$DELLNM function. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7822 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspscm: SYS$CREMBX failure |
| Long Text: | An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7823 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspsqr: $QIO failure |
| Long Text: | An error was returned from $QIO while trying to queue a read to the process dump mailbox. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7824 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspain: $SETIMR failure |
| Long Text: | An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7825 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspsck: $QIO failure at AST level |
| Long Text: | An error was returned from SYS$QIO while trying to read the process dump mailbox. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7826 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sspscm: SYS$GETDVIW failure |
| Long Text: | An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7840 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: LIB$GET_VM failure |
| Long Text: | An error was returned from LIB$GET_VM while attempting to allocate memory for an I/O vector. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7841 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: SYS$OPEN failure |
| Long Text: | An error was returned from SYS$OPEN while attempting to open the datafile for reading. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7842 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfcl: SYS$CLOSE failure |
| Long Text: | An error was returned from SYS$CLOSE while attempting to close the input datafile. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7843 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfcl: LIB$FREE_VM failure |
| Long Text: | An error was returned from LIB$FREE_VM while attempting to free the memory for the I/O vector. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7844 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: LIB$GET_VM failure |
| Long Text: | An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7845 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfcl: LIB$FREE_VM failue |
| Long Text: | An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7846 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: %s byte record too big for %s byte user buffer |
| Long Text: | The longest record in the file will not fit into the largest data buffer that can be allocated. |
| Repair Text: | From Oracle doc: Modify the RMS file to have smaller records. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7847 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: $CONNECT failure |
| Long Text: | An error was returned by SYS$CONNECT while attempting to open the datafile. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7848 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfrb: $GET failure |
| Long Text: | An error was returned by SYS$GET while attempting to read the datafile. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7849 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfsk: $GET failure |
| Long Text: | An error was returned by SYS$GET while attempting to skip records in the input file. |
| Repair Text: | From Oracle doc: Check system error and refer to VMS documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7850 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: bad option |
| Long Text: | You are using a bad option to loader Fixed= is one legal option. Check documentation for others. |
| Repair Text: | From Oracle doc: Check documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7860 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnsoi: error setting up interrupt handler |
| Long Text: | An error occurred while setting up the control interrupt handler. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-7880 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sdopnf: internal error |
| Long Text: | A list of all files open by this process could not be obtained. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of session sequence lists exceeded |
| Long Text: | The sequence parent state objects for this session are all used. This is an internal error. |
| Repair Text: | From Oracle doc: Quit the session and begin a new one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence %s.CURRVAL is not yet defined in this session |
| Long Text: | Sequence CURRVAL has been selected before sequence NEXTVAL. |
| Repair Text: | From Oracle doc: Select NEXTVAL from the sequence before selecting CURRVAL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence %s.NEXTVAL exceeds internal limits |
| Long Text: | The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal representation size. |
| Repair Text: | From Oracle doc: Alter or re-create the sequence number with legal limits. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequence %s.NEXTVAL %s stringVALUE and cannot be instantiated |
| Long Text: | Instantiating NEXTVAL would violate one of MAX/MINVALUE. |
| Repair Text: | From Oracle doc: Alter the sequence so that a new value can be requested. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified row does not exist |
| Long Text: | A row with the given ROWID does not exist in any of the tables given. |
| Repair Text: | From Oracle doc: Check the query for misspellings of table names and the ROWID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified row no longer exists |
| Long Text: | The row has been deleted by another user since the operation began. |
| Repair Text: | From Oracle doc: Retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | another instance is mounted with USE_ROW_ENQUEUES = %s |
| Long Text: | The shared instance being started does not have the same value for USE_ROW_ENQUEUES as already running instances. |
| Repair Text: | From Oracle doc: Ensure that all instances' INIT.ORA files specify the same value for the parameter USE_ROW_ENQUEUES. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index is not valid - see trace file for diagnostics |
| Long Text: | Validate Index detected an inconsistency in its argument index. |
| Repair Text: | From Oracle doc: Send trace file to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index key does not exist root dba %s, dba %s (%s) |
| Long Text: | This is an internal error; possible inconsistency in index. |
| Repair Text: | From Oracle doc: Send trace file to Oracle Customer Support, along with information on reproducing the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index key not found, obj# %s, dba %s (%s) |
| Long Text: | This is an internal error; possible inconsistency in index. |
| Repair Text: | From Oracle doc: Send trace file to Oracle Customer Support, along with information on reproducing the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object no longer exists |
| Long Text: | The object has been deleted by another user since the operation began. |
| Repair Text: | From Oracle doc: Remove references to the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8104 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | this index object %s is being online built or rebuilt |
| Long Text: | The index is being created or rebuild or waited for recovering from the online (re)build. |
| Repair Text: | From Oracle doc: Wait the online index build or recovery to complete. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle event to turn off smon cleanup for online index build |
| Long Text: | Set this event only under the supervision of Oracle development. |
| Repair Text: | From Oracle doc: Debugging only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not create journal table %s.%s |
| Long Text: | Online index builder cannot create its journal table. |
| Repair Text: | From Oracle doc: Rename your table in conflict. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | may not build or rebuild this type of index online |
| Long Text: | Only support normal index or IOT top-level index. |
| Repair Text: | From Oracle doc: Change your index type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | nosort is not a supported option for online index build |
| Long Text: | May not specify NOSORT for online index build. |
| Repair Text: | From Oracle doc: Get rid of NOSORT in the index creation command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle event to test SMON cleanup for online index build |
| Long Text: | Oracle Kernel test only. |
| Repair Text: | From Oracle doc: Do not set this event (for test only). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a partitioned index may not be coalesced as a whole |
| Long Text: | User attempted to coalesce a partitioned index using ALTER INDEX COALESCE statement, which is illegal. |
| Repair Text: | From Oracle doc: Coalesce the index a (sub)partition at a time (using ALTER INDEX MODIFY (sub)PARTITION COALESCE). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a composite partition may not be coalesced as a whole |
| Long Text: | User attempted to coalesce a composite partition. |
| Repair Text: | From Oracle doc: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | composite partition index may not be compressed |
| Long Text: | User attempted to compress a composite partition index. |
| Repair Text: | From Oracle doc: Create uncompressed composite partition index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not alter a fake index |
| Long Text: | An attempt was made to alter a fake index. |
| Repair Text: | From Oracle doc: Drop the fake index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not online create/rebuild this index type |
| Long Text: | User attempted to create index type that online does not support. |
| Repair Text: | From Oracle doc: Use offline index create/rebuild command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not acquire dml enough lock(S mode) for online index build |
| Long Text: | User attempted to create index online without allowing DML Share lock. |
| Repair Text: | From Oracle doc: Allow DML share lock on the base table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8175 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | discrete transaction restriction violated (%s) |
| Long Text: | An attempt was made to perform an action that is not currently supported in a discrete transaction. |
| Repair Text: | From Oracle doc: Roll back the transaction, and retry it as a normal transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8176 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | consistent read failure; rollback data not available |
| Long Text: | Encountered data changed by an operation that does not generate rollback data: create index, direct load or discrete transaction. |
| Repair Text: | From Oracle doc: In read/write transactions, retry the intended operation. Read-only transactions must be restarted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8177 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can't serialize access for this transaction |
| Long Text: | Encountered data changed by an operation that occurred after the start of this serializable transaction. |
| Repair Text: | From Oracle doc: In read/write transactions, retry the intended operation or transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8178 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal SERIALIZABLE clause specified for user INTERNAL |
| Long Text: | Serializable mode is not supported for user INTERNAL. |
| Repair Text: | From Oracle doc: Reconnect as another user and retry the SET TRANSACTION command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8179 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | concurrency check failed |
| Long Text: | Encountered data changed by an operation that occurred after a specific snapshot. This is usually used to indicate that a particular cached copy of a data block is stale. This is used for internal use for now. |
| Repair Text: | From Oracle doc: Refresh the cached copy of the data block and retry operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scggc: failed to open lock |
| Long Text: | The Lock Manager failed to open a lock. |
| Repair Text: | From Oracle doc: Check if enough memory is available and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scggc: failed to convert lock |
| Long Text: | The Lock Manager failed to convert a lock. |
| Repair Text: | From Oracle doc: Retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcc: failed to close lock |
| Long Text: | The Lock Manager encountered an error closing a lock. |
| Repair Text: | From Oracle doc: Check the Lock Manager status returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcan: failed to cancel a pending convert request |
| Long Text: | The Lock Manager encountered an error cancelling a convert request. |
| Repair Text: | From Oracle doc: Check the Lock Manager status returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcm: unexpected lock manager return code |
| Long Text: | The Lock Manager returned an unexpected value. |
| Repair Text: | From Oracle doc: Check the Lock Manager status returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: $ORACLE_SID not set in environment |
| Long Text: | The environment variable ORACLE_SID is not set. |
| Repair Text: | From Oracle doc: Set the ORACLE_SID environment variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: cannot translate address file name |
| Long Text: | Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf. |
| Repair Text: | From Oracle doc: Ensure that ORACLE_HOME and ORACLE_SID are properly set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: cannot open address file |
| Long Text: | The address file could not be opened. |
| Repair Text: | From Oracle doc: Check that Oracle is up. Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has correct permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: cannot read from address file |
| Long Text: | The address file could not be read. |
| Repair Text: | From Oracle doc: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and contains a single line of text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scngrs: SCN not yet initialized |
| Long Text: | The System Commit Number has not yet been initialized. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Requested I/O error |
| Long Text: | Oracle requested that an I/O error be returned for this operation. |
| Repair Text: | From Oracle doc: This should not occur in normal Oracle operation. Contact support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: failed to allocate SGA |
| Long Text: | The N_CORE system call failed, maybe due to insufficient memory. |
| Repair Text: | From Oracle doc: Specify a smaller number of buffers. Check INIT.ORA parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: unable to attach to SGA |
| Long Text: | The process cannot attach to the SGA. This can happen if either the listener cannot attach, or the process cannot communicate with the listener. |
| Repair Text: | From Oracle doc: Verify that the instance is up and running. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdes: cannot detach from SGA |
| Long Text: | Probably the listener process has died. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdes: cannot unmap SGA |
| Long Text: | The N_CORE system call failed while detaching from the SGA. |
| Repair Text: | From Oracle doc: Note NCX error returned; contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: cannot get instance listener address |
| Long Text: | The instance listener address cannot be read from the SGADEF file. |
| Repair Text: | From Oracle doc: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Additional information gives error return from ORA_ADDR. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: listener not on this node |
| Long Text: | A process wishing to attach to the SGA is on a different node from its instance's listener. |
| Repair Text: | From Oracle doc: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8236 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: cannot share subcube with listener |
| Long Text: | The N_SHARE call failed, probably because the listener has died. |
| Repair Text: | From Oracle doc: Check if the listener is running, and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8237 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: SGA region not yet created |
| Long Text: | An attempt was made to attach to an SGA which has not yet been created. |
| Repair Text: | From Oracle doc: Verify that the instance is running. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8238 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsfre: cannot detach from SGA |
| Long Text: | The N_CORE system call failed while detaching from the SGA. |
| Repair Text: | From Oracle doc: Check NCX error, and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8240 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snlmatt: parallel server name too long |
| Long Text: | The file name of the Lock Manager address file is too long. |
| Repair Text: | From Oracle doc: Use a shorter parallel server name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8241 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snlmatt: cannot attach to lock manager |
| Long Text: | Failed to attach to Lock Manager, perhaps because it is not running. |
| Repair Text: | From Oracle doc: Additional information is Lock Manager return code. Check that Lock Manager is running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8242 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snlmdet: cannot detach from lock manager |
| Long Text: | An error was encountered detaching from the Lock Manager. |
| Repair Text: | From Oracle doc: Additional information is Lock Manager return code. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: cannot open nameserver |
| Long Text: | A process could not connect to the name server. |
| Repair Text: | From Oracle doc: Make sure the name server is up and running. Additional information gives name server's returned status. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: cannot find name in nameserver |
| Long Text: | The listener name server entry for an instance could not be found. |
| Repair Text: | From Oracle doc: Make sure the name server is up and running. Additional information gives name server's returned status. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: ORACLE_PSRV undefined |
| Long Text: | The parallel server name ORACLE_PSRV was undefined. |
| Repair Text: | From Oracle doc: Set the environment variable ORACLE_PSRV and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: cannot free listener address |
| Long Text: | The listener name server entry could not be freed. |
| Repair Text: | From Oracle doc: Additional information gives name server's returned status. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8264 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ora_addr: cannot close nameserver |
| Long Text: | The connection to the name server could not be closed. |
| Repair Text: | From Oracle doc: Additional information gives name server's returned status. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | create_ora_addr: cannot open nameserver |
| Long Text: | A process could not connect to the name server. |
| Repair Text: | From Oracle doc: Make sure the name server is up and running. Additional information gives name server's returned status. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | create_ora_addr: cannot register name in nameserver |
| Long Text: | The listener's addressing information could not be registered. |
| Repair Text: | From Oracle doc: Make sure the name server is up and running. Additional information gives name server's returned status. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8267 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | destroy_ora_addr: cannot close nameserver |
| Long Text: | The connection to the name server could not be closed. |
| Repair Text: | From Oracle doc: Additional information gives name server's returned status. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8268 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | create_ora_addr: cannot close nameserver |
| Long Text: | The connection to the name server could not be closed. |
| Repair Text: | From Oracle doc: Additional information gives name server's returned status. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8269 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | destroy_ora_addr: cannot destroy name |
| Long Text: | The listener's addressing information could not be removed. |
| Repair Text: | From Oracle doc: Additional information gives name server's returned status. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksachk: Illegal archival control %s |
| Long Text: | Archive files cannot be created with the given archival control string. |
| Repair Text: | From Oracle doc: Check that the volume exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksabln: Buffer size not large enough for archive control %s |
| Long Text: | The given archival control string expands into too many characters. |
| Repair Text: | From Oracle doc: Reduce archive control string length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8274 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Out of memory for environment variable |
| Long Text: | There is insufficient memory to return the requested value. |
| Repair Text: | From Oracle doc: Reduce memory usage and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8275 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Environment variable unset |
| Long Text: | The requested environment variable is not set. |
| Repair Text: | From Oracle doc: Ensure that the variable name requested is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No room in nameserver for pid |
| Long Text: | There is no room to record the PID for a background process. |
| Repair Text: | From Oracle doc: SHUTDOWN ABORT and restart the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot set environment variable |
| Long Text: | There is insufficient memory to expand the environment. |
| Repair Text: | From Oracle doc: Reduce memory usage and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot get CPU statistics |
| Long Text: | Could not retrieve CPU times because N_STAT failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8308 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: Cannot open file |
| Long Text: | Oracle could not open a file. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: Cannot fstat file |
| Long Text: | Oracle could not obtain information about an open file. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: Bad value for recsize |
| Long Text: | An illegal value for the record size was specified. |
| Repair Text: | From Oracle doc: Specify a value for the RECSIZE option that is greater than 0. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: bad value for maxrecsize |
| Long Text: | An illegal value for the maximum record size was specified. |
| Repair Text: | From Oracle doc: Specify a value for the MAXRECSIZE option that is greater than 0. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8312 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: unrecognized processing option |
| Long Text: | An unrecognized processing option was specified. |
| Repair Text: | From Oracle doc: Check the Oracle for nCUBE 2 User's Guide for valid options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: could not allocate buffers |
| Long Text: | Memory for the load buffers could not be allocated. |
| Repair Text: | From Oracle doc: Reduce the maximum record size. Eliminate any unnecessary processes on your current node before running SQL*Loader again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfcf: Error closing file |
| Long Text: | An error occurred trying to close a file. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfrb: Error reading file |
| Long Text: | An error occurred trying to read from a file. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfsk: Error seeking in file. |
| Long Text: | The LSEEK system call returned an error. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfsk: Error seeking in file. |
| Long Text: | The LSEEK system call returned an error. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfsk: Error reading file |
| Long Text: | An error occurred trying to read from a file. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfsk: Error reading file |
| Long Text: | An error occurred trying to read from a file. |
| Repair Text: | From Oracle doc: Check the UNIX errno returned as additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8320 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scnget: Call to scnget before scnset or scnfnd. |
| Long Text: | This is an internal error |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scnmin: NOT IMPLEMENTED YET |
| Long Text: | This is an internal error |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scnmin: open/convert of bias lock failed |
| Long Text: | A call to the LKMGR failed to open and convert the bias lock. |
| Repair Text: | From Oracle doc: Check to make sure the LKMGR is up. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8323 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scnmin: close of bias lock failed |
| Long Text: | A call to the LKMGR failed to close the bias lock. |
| Repair Text: | From Oracle doc: Check to make sure the LKMGR is up. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8330 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Printing not supported |
| Long Text: | An attempt was made to automatically spool a file to the printer. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8331 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Wait operation timed out |
| Long Text: | Oracle timed out waiting for an event. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8332 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rollback segment #%s specified not available |
| Long Text: | See ORA-01545. |
| Repair Text: | From Oracle doc: See ORA-1545. Also, make sure you have created enough rollback segments for the number of instances you are trying to start. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | This command not allowed on nCUBE, only one thread is ever used. |
| Long Text: | An illegal command was executed for the nCUBE platform. |
| Repair Text: | From Oracle doc: There is no need to issue this command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | On nCUBE, this command can only be executed from instance 1. |
| Long Text: | A command that can only be issued on instance 1 was issued elsewhere. |
| Repair Text: | From Oracle doc: Log on to instance 1 and repeat the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sropen: failed to open a redo server connection |
| Long Text: | An error occurred trying to connect to the redo server. |
| Repair Text: | From Oracle doc: The operating system-specific error message should tell you what to do. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8343 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | srclose: failed to close a redo server connection |
| Long Text: | An error occurred trying to close the redo server connection. |
| Repair Text: | From Oracle doc: The operating system-specific error message should tell you what to do. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | srapp: failed to send redo data to the redo server |
| Long Text: | An error occurred trying to send redo to the redo server. |
| Repair Text: | From Oracle doc: The operating system-specific error message should tell you what to do. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcm: Out of memory in lock manager. |
| Long Text: | The Lock Manager ran out of memory. |
| Repair Text: | From Oracle doc: Reduce the number of locks specified in the GC_FILES_TO_LOCKS and GC_ROLLBACK_LOCKS initialization parameters or increase the number of Lock Manager processes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid compiler name: %s |
| Long Text: | An invalid compiler name comp_name was passed to a UTL_PG conversion routine. |
| Repair Text: | From Oracle doc: Correct the compiler name parameter in the PL/SQL code that called the conversion routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8412 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message |
| Long Text: | The WMSGBSIZ is the maximum size for warning message block, it is recommended to be 1024 bytes to 8 kilobytes. |
| Repair Text: | From Oracle doc: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8413 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid compiler type in FORMAT parameter at %s |
| Long Text: | An invalid compiler type is defined in format control block. The format control block is invalid. |
| Repair Text: | From Oracle doc: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8414 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error encountered in %s |
| Long Text: | The function routine returned an error. Where routine may be: RAW_TO_NUMBER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT MAKE_RAW_TO_NUMBER_FORMAT |
| Repair Text: | From Oracle doc: This message will be preceded by messages providing details about the error. Check those messages to determine what action to take. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8429 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw data has invalid digit in display type data |
| Long Text: | The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit. |
| Repair Text: | From Oracle doc: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw data missing leading sign |
| Long Text: | The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign. |
| Repair Text: | From Oracle doc: Correct the input raw data or the mask options so that they match. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw data missing zero as defined in picture |
| Long Text: | The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero. |
| Repair Text: | From Oracle doc: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw data has invalid floating point data |
| Long Text: | The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data. |
| Repair Text: | From Oracle doc: Correct the input raw data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid picture type in convert raw to number |
| Long Text: | The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8434 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw data has invalid trailing sign |
| Long Text: | The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign. |
| Repair Text: | From Oracle doc: Correct the input raw data or the mask options so that they match. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8435 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PICTURE MASK missing the leading sign when SIGN IS LEADING specified |
| Long Text: | The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign. |
| Repair Text: | From Oracle doc: Correct the input raw data or the mask options so that they match. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw data has invalid sign digit |
| Long Text: | The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign. |
| Repair Text: | From Oracle doc: Correct the input raw data or the picture mask so that they match. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid picture type in picture mask |
| Long Text: | The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw buffer is too short to hold converted data |
| Long Text: | The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask. |
| Repair Text: | From Oracle doc: Increase the raw buffer size to the size necessary to hold the entire result of the conversion. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | closed parenthesis missing in picture mask |
| Long Text: | A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine. |
| Repair Text: | From Oracle doc: Correct the picture mask. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in BLANK WHEN ZERO clause in mask options |
| Long Text: | A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: BLANK ZERO BLANK ZEROS BLANK ZEROES BLANK WHEN ZERO BLANK WHEN ZEROS BLANK WHEN ZEROES |
| Repair Text: | From Oracle doc: Correct the mask options parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in JUSTIFIED clause in mask options |
| Long Text: | A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: JUST JUST RIGHT JUSTIFIED JUSTIFIED RIGHT |
| Repair Text: | From Oracle doc: Correct the mask options parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8445 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in SIGN clause in mask options |
| Long Text: | A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SIGN LEADING SIGN LEADING SEPARATE SIGN LEADING SEPARATE CHARACTER SIGN TRAILING SIGN TRAILING SEPARATE SIGN TRAILING SEPARATE CHARACTER SIGN IS LEADING SIGN IS LEADING SEPARATE SIGN IS LEADING SEPARATE CHARACTER SIGN IS TRAILING SIGN IS TRAILING SEPARATE SIGN IS TRAILING SEPARATE CHARACTER |
| Repair Text: | From Oracle doc: Correct the mask options parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in SYNCHRONIZED clause in mask options |
| Long Text: | A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SYNC SYNC LEFT SYNC RIGHT SYNCHRONIZED SYNCHRONIZED LEFT SYNCHRONIZED RIGHT |
| Repair Text: | From Oracle doc: Correct the mask options parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8447 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in USAGE clause in mask options |
| Long Text: | A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: USAGE DISPLAY USAGE COMP USAGE COMP-3 USAGE COMP-4 USAGE COMPUTATIONAL USAGE COMPUTATIONAL-3 USAGE COMPUTATIONAL-4 USAGE IS DISPLAY USAGE IS COMP USAGE IS COMP-3 USAGE IS COMP-4 USAGE IS COMPUTATIONAL USAGE IS COMPUTATIONAL-3 USAGE IS COMPUTATIONAL-4 |
| Repair Text: | From Oracle doc: Correct the mask options parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8448 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in DECIMAL-POINT environment clause |
| Long Text: | A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA. |
| Repair Text: | From Oracle doc: Correct the environment clause parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid numeric symbol found in picture mask |
| Long Text: | An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8450 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid specification of CR in picture mask |
| Long Text: | The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid specification of DB in picture mask |
| Long Text: | The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specification of E in picture mask is unsupported |
| Long Text: | The floating point exponent symbol 'E' was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter, and the data, if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | more than one V symbol specified in picture mask |
| Long Text: | The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator ('V'). Only one decimal point indicator is allowed in the picture mask. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8454 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | more than one S symbol specified in picture mask |
| Long Text: | The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator ('S'). Only one operational sign indicator is allowed in the picture mask. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8455 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in CURRENCY SIGN environment clause |
| Long Text: | A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x where x is a valid currency sign. |
| Repair Text: | From Oracle doc: Correct the environment clause parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8456 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no sign in picture mask but SIGN clause in mask options |
| Long Text: | The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol ('S', '+', or '-'), but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause. |
| Repair Text: | From Oracle doc: Correct the picture mask parameter or the mask options parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8457 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in SEPARATE CHARACTER option of SIGN clause |
| Long Text: | A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE, SEPARATE CHARACTER. |
| Repair Text: | From Oracle doc: Correct the mask options parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8458 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid format parameter |
| Long Text: | The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT. |
| Repair Text: | From Oracle doc: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8459 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid format parameter length |
| Long Text: | The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length. |
| Repair Text: | From Oracle doc: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8460 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid environment clause in environment parameter |
| Long Text: | The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported. |
| Repair Text: | From Oracle doc: Correct the environment parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8462 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw buffer contains invalid decimal data |
| Long Text: | The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data. |
| Repair Text: | From Oracle doc: Correct the input data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8463 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | overflow converting decimal number to Oracle number |
| Long Text: | The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number. |
| Repair Text: | From Oracle doc: Be sure that the input decimal number is valid, and be sure that the output variable is large enough to hold the Oracle number value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8464 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input raw decimal data contains more than 42 digits |
| Long Text: | The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number. |
| Repair Text: | From Oracle doc: Correct the raw input buffer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8465 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input mask contains more than 32 characters |
| Long Text: | The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters. |
| Repair Text: | From Oracle doc: Correct the mask input buffer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8466 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | raw buffer length %s is too short for %s |
| Long Text: | The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than string bytes long, but the picture mask parameter specified that string bytes of input data were to be converted. |
| Repair Text: | From Oracle doc: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8467 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error converting Oracle number to %s |
| Long Text: | An error occurred when converting an Oracle number to a COBOL type of: DISPLAY COMP-3 or character variable. The Oracle number was not in the correct format. |
| Repair Text: | From Oracle doc: Correct the call to the conversion routine. The input must be a valid Oracle number variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8468 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | mask option %s is not supported |
| Long Text: | The mask option clause was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The clause can be: USAGE IS POINTER USAGE IS INDEX USAGE IS COMP-1 USAGE IS COMP-2 POINTER |
| Repair Text: | From Oracle doc: Remove the clause from the mask options parameter in the PL/SQL call to UTL_PG. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8498 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | Warning: picture mask '%s' overrides picture mask option 'USAGE IS %s' to 'USAGE IS DISPLAY' |
| Long Text: | Picture mask USAGE option was overridden by the picture mask. |
| Repair Text: | From Oracle doc: This is an informational message only. The message may be eliminated by changing the USAGE option to match the picture mask. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-8499 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | Warning: picture mask options '%s' ignored by UTL_PG |
| Long Text: | Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines. |
| Repair Text: | From Oracle doc: This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfccf: error creating file |
| Long Text: | Could be out of disk space. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfcopy: error copying file |
| Long Text: | Block sizes may not match. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfifi: error identifying file |
| Long Text: | DB_BLOCK_SIZE specified in the INIT.ORA file could be incorrect. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfofi: error opening file |
| Long Text: | File attributes may have changed. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfotf: error opening temporary file |
| Long Text: | Incorrect path may have been specified for the file. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfqio: error reading or writing to disk |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfrfb: error reading from file |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfsrd: error reading from file |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftcls: error closing file |
| Long Text: | File may have been corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftget: error reading from file |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sftopn: error opening file |
| Long Text: | Incorrect path may have been specified for the file. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfwfb: error writing to file |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfwfbmt: error writing to file |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgfn: error fabricating file name |
| Long Text: | File name may be too long. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfdone: I/O error detected |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfqio: error detected in IOCompletionRoutine |
| Long Text: | File may have been truncated or corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sdnfy: bad value '%s' for parameter %s |
| Long Text: | The directory specified as the value for the stated parameter could not be used. |
| Repair Text: | From Oracle doc: Make sure the directory you have specified is a valid directory/file specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfsfs: failed to resize file |
| Long Text: | Could be out of disk space. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfrfs: failed to refresh file size |
| Long Text: | File may be corrupted or truncated. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9240 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpalo: error allocating PGA memory |
| Long Text: | Could be out of memory. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9241 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsalo: error allocating SGA memory |
| Long Text: | Could be out of memory. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9242 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: error creating SGA |
| Long Text: | An error occurred while creating SGA. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9243 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: error attaching to SGA |
| Long Text: | SGA may not have been created (database not started). |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9244 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smprset: error setting memory protections |
| Long Text: | An error occurred while setting memory protections. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9245 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smcstk: error switching stacks |
| Long Text: | An error occurred while switching stacks. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9246 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sfsmap: unable to map SGA |
| Long Text: | Unable to map SGA. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9247 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsdes: error destroying the SGA |
| Long Text: | An error occurred while destroying the SGA. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sigpidu: error obtaining process id |
| Long Text: | May be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdcr: error creating detached (background) process |
| Long Text: | Could be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spdde: error terminating detached (background) process |
| Long Text: | Could be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spini: error initializing process |
| Long Text: | Could be out of memory. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9264 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sptpa: error flagging process |
| Long Text: | Could be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: error temporarily suspending process |
| Long Text: | Could be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spawn: error starting an Oracle process |
| Long Text: | Could be out memory. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szalloc: error allocating memory for security |
| Long Text: | Could be out of memory. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szlon: error verifying user name |
| Long Text: | Username may be too long. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9272 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote os logon is not allowed |
| Long Text: | Remote operating system login attempted when not allowed. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9273 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrfc: error verifying role name |
| Long Text: | An operating system error was returned when verifying the role name. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9274 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrfc: insufficient role name buffer space |
| Long Text: | An OS role name was too long. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9280 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfcf: error closing file |
| Long Text: | File may be corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: error opening file |
| Long Text: | Possibly incorrect path specified to the file. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9282 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfrb: error reading records |
| Long Text: | File could be corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9283 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfsk: error skipping records |
| Long Text: | File could be corrupted. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9284 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: cannot allocate read buffer |
| Long Text: | MALLOC() system call returned an error. The system might have run out of heap space. |
| Repair Text: | From Oracle doc: Check additional information for the operating system error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9285 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: unrecognizable processing option, incorrect format |
| Long Text: | Processing option passed is of incorrect format. |
| Repair Text: | From Oracle doc: Consult your IUG for permissible formats. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksaalo: error allocating memory for archival |
| Long Text: | Could be out of memory. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9291 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksachk: invalid device specified for archive destination |
| Long Text: | Unable to access directory. |
| Repair Text: | From Oracle doc: Specify a valid device in ARCHIVE control string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9292 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksabln: unable to build archive file name |
| Long Text: | Bad directory or format specified. |
| Repair Text: | From Oracle doc: Specify a valid directory in LOG_ARCHIVE_FORMAT and a valid format string in LOG_ARCHIVE_FORMAT in the INIT.ORA file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9293 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sksasmo: unable to send message to console |
| Long Text: | An error was returned while attempting to send a message to the console operator. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osncon: unable to connect, DPMI not available |
| Long Text: | Unable to detect the presence of DPMI. |
| Repair Text: | From Oracle doc: Restart Windows and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osncon: local kernel only supported in standard mode |
| Long Text: | An attempt was made to connect to S: while in enhanced mode. |
| Repair Text: | From Oracle doc: Restart Windows in standard mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sclgt: error freeing latch |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsleep: error temporarily suspending process |
| Long Text: | May be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9312 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slspool: error spooling file to printer |
| Long Text: | Could be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsprom: error prompting user |
| Long Text: | May be out of resources. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sltln: error translating logical name |
| Long Text: | Internal buffer may have overflowed. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sql2tt: two-task error translating ORACLE_EXECUTABLE |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrpc: unable to verify password for role |
| Long Text: | OS roles may not be supported for this platform. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szprv: insufficient privileges |
| Long Text: | The password specified is invalid. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slkhst: unable to host out to operating system |
| Long Text: | There might not be enough memory for the command or hosting out may not be supported on this platform. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slgtd: unable to obtain the current date and time |
| Long Text: | The system time might be set incorrectly. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9320 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrfc: unable to obtain the list of valid OS roles |
| Long Text: | OS roles may not be supported on this platform. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slzdtb: unable to convert zoned decimal to binary |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slpdtb: unable to convert packed decimal to binary |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9330 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Session terminated internally by Oracle or by an Oracle DBA |
| Long Text: | A client workstation that is abnormally disconnected would cause Oracle to terminate that session after about a minute. This message also appears in the trace file if a SHUTDOWN ABORT is performed. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9331 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcan: unable to process lk_sync_cancel return code |
| Long Text: | An invalid lock status was returned by the Lock Manager, so the locks may no longer be consistent. |
| Repair Text: | From Oracle doc: Use the UTLLOCK.SQL script to determine your lock status. Refer to the Oracle8i Administrator's Guide for information about the script. If this error occurs frequently, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9332 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcc: unable to process lk_close return code |
| Long Text: | An invalid lock status was returned by the Lock Manager, so the locks may no longer be consistent. |
| Repair Text: | From Oracle doc: Use the UTLLOCK.SQL script to determine your lock status. Refer to the Oracle8i Administrator's Guide for information about the script. If this error occurs frequently, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9333 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scggc: unable to process lk_open_convert return code |
| Long Text: | An invalid lock status was returned by the Lock Manager, so the locks may no longer be consistent. |
| Repair Text: | From Oracle doc: Use the UTLLOCK.SQL script to determine your lock status. Refer to the Oracle8i Administrator's Guide for information about the script. If this error occurs frequently, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9334 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scggc: unable to process lk_convert return code |
| Long Text: | An invalid lock status was returned by the Lock Manager, so the locks may no longer be consistent. |
| Repair Text: | From Oracle doc: Use the UTLLOCK.SQL script to determine your lock status. Refer to the Oracle8i Administrator's Guide for information about the script. If this error occurs frequently, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcm: unable to process return code in completion procedure |
| Long Text: | An invalid lock status was returned by the Lock Manager, so the locks may no longer be consistent. |
| Repair Text: | From Oracle doc: Use the UTLLOCK.SQL script to determine your lock status. Refer to the Oracle8i Administrator's Guide for information about the script. If this error occurs frequently, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Specified ORACLE_SID is either invalid or too long |
| Long Text: | ORACLE_SID must be at the most 4 alphanumeric characters. |
| Repair Text: | From Oracle doc: Specify an ORACLE_SID with the correct format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scumnt: unable to mount database |
| Long Text: | Another instance is currently mounting the database. |
| Repair Text: | From Oracle doc: Try again later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9342 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Detached process terminated by Oracle during shutdown abort |
| Long Text: | The user performed a SHUTDOWN ABORT. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9344 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | spsig: error signalling thread |
| Long Text: | This function may not be implemented. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 32-bit Two-Task driver unable to allocate context area |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 32-bit Two-Task driver unable to allocate shared memory |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 32-bit Two-Task driver unable to spawn new ORACLE task |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 32-bit Two-Task driver unable to open event semaphore |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 32-bit Two-Task driver: ORACLE task unexpectedly died |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to allocate context area |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to lock context area |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to deallocate context area |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver invalid context area |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9364 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to create hidden window |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9365 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to destroy hidden window |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9366 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to allocate shared memory |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9367 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to deallocate shared memory |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9368 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver unable to spawn ORACLE |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver bad instance handle |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9370 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Windows 3.1 Two-Task driver ORACLE task timed out |
| Long Text: | See OSD error accompanying this message. |
| Repair Text: | From Oracle doc: See OSD error accompanying this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9700 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sclin: maximum number of latches exceeded |
| Long Text: | Oracle wants to use more latches then available. |
| Repair Text: | From Oracle doc: Increase the value of the initialization parameter LATCH_PAGES or decrease the amount of shared memory you are using. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scnfy: maximum number of processes exceeded |
| Long Text: | The value of the PROCESSES initialization parameter was exceeded. |
| Repair Text: | From Oracle doc: Decrease the PROCESSES parameter and restart. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sem_acquire: cannot acquire latch semaphore |
| Long Text: | The semaphore used for accessing latches could not be seized. |
| Repair Text: | From Oracle doc: Send trace file to Oracle Customer Support, along with information on reproducing the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sem_release: cannot release latch semaphore |
| Long Text: | The semaphore used for accessing latches could not be released. |
| Repair Text: | From Oracle doc: Send trace file to Oracle Customer Support, along with information on reproducing the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sstascre: ftok error in creating test and set pages. |
| Long Text: | the FTOK() library call failed in SSTASTCRE(). |
| Repair Text: | From Oracle doc: Verify that TASDEF@.DBF file exists. If it does then this is a possible system failure. Perhaps System V compatibility is not enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spcre: cannot initialize latch semaphore |
| Long Text: | The semaphore used for accessing latches could not be initialized. |
| Repair Text: | From Oracle doc: Send trace file to Oracle Customer Support, along with information on reproducing the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: get_process_stats error. |
| Long Text: | GET_PROCESS_STATS system call returned an error. Possible operating system error. |
| Repair Text: | From Oracle doc: Check additional information returned. Look for information in operating system reference. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: failed to bind socket to port. |
| Long Text: | The bind system call failed on the socket. |
| Repair Text: | From Oracle doc: Check additional information for operating system error. Try connecting again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: failed to accept a connection. |
| Long Text: | The accept system call failed on the socket. |
| Repair Text: | From Oracle doc: Check additional information for operating system error. Try connecting again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9710 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soarcv: buffer overflow. |
| Long Text: | The internal buffer is not big enough to hold the message read. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9711 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | orasrv: archmon already connected. |
| Long Text: | An existing connection has already been made from ARCHMON to ORASRV. |
| Repair Text: | From Oracle doc: Stop trying to connect. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9712 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | orasrv: log archiver already connected. |
| Long Text: | An existing connection has already been made from log archiver to ORASRV. |
| Repair Text: | From Oracle doc: Stop trying to connect. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9713 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Global hardware clock failure caused instance termination. |
| Long Text: | The global hardware clock used to generate the System Change Number for Oracle has failed. |
| Repair Text: | From Oracle doc: Check the global hardware clock. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9714 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Two Task interface: cannot obtain puname |
| Long Text: | The TXIPC driver cannot obtain the name of the PU. (Possible operating system error.) |
| Repair Text: | From Oracle doc: Check if the PUs are named (consistent). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9715 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | orasrv: cannot obtain puname |
| Long Text: | ORASRV cannot obtain the name of the PU (possible operating system error). |
| Repair Text: | From Oracle doc: Check if the PUs are named (consistent). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9716 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | kslcll: Unable to fix in-flux lamport latch. |
| Long Text: | One Oracle process died while still holding a LAMPORT latch. |
| Repair Text: | From Oracle doc: Exit (kill) all Oracle user processes. SHUTDOWN ABORT and restart Oracle RDBMS kernel. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9717 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnsui: maximum number of user interrupt handlers exceeded. |
| Long Text: | The internal limit on the number of user interrupt handlers has been exceeded. |
| Repair Text: | From Oracle doc: Reduce the number of simultaneous logons or reduce the number of user interrupt handlers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9718 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnsui: cannot set up user interrupt handler. |
| Long Text: | MALLOC() failed to allocate space to hold user interrupt handler. |
| Repair Text: | From Oracle doc: Possible memory resource shortage. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9719 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osncui: invalid handle. |
| Long Text: | The handle passed to OSNCUI is out of the valid range. |
| Repair Text: | From Oracle doc: Use a valid handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9740 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slsget: cannot get virtual memory region statistics. |
| Long Text: | The VM_REGION system call failed to get virtual memory region statistics. |
| Repair Text: | From Oracle doc: Check return code in SERCERRNO. Possible operating system failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9741 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: error waiting for a post. |
| Long Text: | MSG_RECEIVE system call returned an error. This is an internal error. |
| Repair Text: | From Oracle doc: Check return code in SERCERRNO. Port name is returned in sercose[0]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9742 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppst: error during a post. |
| Long Text: | MSG_SEND system call returned an error. This is an internal error. |
| Repair Text: | From Oracle doc: Check return code in SERCERRNO. Port name is returned in sercose[0]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9743 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: could not attach shared memory. |
| Long Text: | The MMAP or write system call returned an error. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9744 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smsget: mmap returned an error. |
| Long Text: | The MMAP system call returned an error. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9745 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: vm_allocate error, unable to create shared memory. |
| Long Text: | Error in system call VM_ALLOCATE. Failed to create SGA as a single shared memory segment. |
| Repair Text: | From Oracle doc: Check result code returned in SERCERRNO. Verify that the SGA attach address is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9746 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smscre: shared memory attach address incorrect. |
| Long Text: | The VM_ALLOCATE system call attached the SGA at an incorrect location. |
| Repair Text: | From Oracle doc: Verify that the SGA attach address is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9747 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pw_detachPorts: server call pws_detach failed. |
| Long Text: | The call PWS_DETACH to (Oracle helper) failed. |
| Repair Text: | From Oracle doc: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9748 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pws_look_up: fork failed |
| Long Text: | The PWS_LOOK_UP call could not fork the (Oracle helper) process. |
| Repair Text: | From Oracle doc: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9749 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pws_look_up: port lookup failure |
| Long Text: | The PWS_LOOK_UP could not find a port to (Oracle helper). |
| Repair Text: | From Oracle doc: Make sure the (Oracle helper) server has been started correctly by PWS_LOOK_UP, and that the network name server is still running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9750 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pw_attachPorts: port_rename failed. |
| Long Text: | The PORT_RENAME system call failed; possible internal error. |
| Repair Text: | From Oracle doc: Check return code in SERCERRNO, report to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9751 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pw_attachPorts: server call pws_attach failed. |
| Long Text: | The call PWS_ATTACH to (Oracle helper) failed. |
| Repair Text: | From Oracle doc: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9752 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pw_attachPorts: port_allocate failed. |
| Long Text: | The PORT_ALLOCATE system call failed; possible resource exhaustion. |
| Repair Text: | From Oracle doc: Check return code in SERCERRNO, report to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9753 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spwat: invalid process number. |
| Long Text: | Function was passed an invalid Oracle process ID. This is an internal error. |
| Repair Text: | From Oracle doc: Additional information indicates the invalid process ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9754 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sppst: invalid process number passed to sppst. |
| Long Text: | Function was passed an invalid Oracle process ID. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9755 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osngpn: port allocation failure. |
| Long Text: | The PORT_ALLOCATE system call failed. |
| Repair Text: | From Oracle doc: Possible system resource shortage; check the error code in SERCERRNO. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9756 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpns: no port in the name server. |
| Long Text: | OSNPNS could not find the given named port in the name server. |
| Repair Text: | From Oracle doc: Check the error code in SERCERRNO. Make sure the shadow process and network name server are still running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9757 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnipn: port allocation failure. |
| Long Text: | The PORT_ALLOCATE system call failed. |
| Repair Text: | From Oracle doc: Possible system resource shortage; check the error code in SERCERRNO. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9758 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnipn: could not check port in name server. |
| Long Text: | The NETNAME_CHECK_IN call failed. |
| Repair Text: | From Oracle doc: Check the error code in SERCERRNO. Make sure the network name server is running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9759 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnsbt: bad message received. |
| Long Text: | The MSG_RECEIVE system call failed, or received a bad message. This is an internal error. |
| Repair Text: | From Oracle doc: Report the error code returned in SERCERRNO. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9760 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpui: cannot send break message |
| Long Text: | The Pipe driver could not send a break message to the Oracle shadow process break thread. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9761 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pw_destroyPorts: server call pws_stop_instance failed. |
| Long Text: | The call PWS_STOP_INSTANCE to (Oracle helper) failed. |
| Repair Text: | From Oracle doc: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9762 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sNeXT_instanceName: translation error. |
| Long Text: | A failure was detected while translating the value of ORACLE_SID. |
| Repair Text: | From Oracle doc: Make sure ORACLE_SID is defined, and that it is of legal length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9763 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmpx: send/receive error exchanging Mach ports. |
| Long Text: | The Mach driver failed to exchange port information with the other side of the connection. Either MSG_SEND (sercose[0] == 1) or MSG_RECEIVE (sercose[0] == 2) failed. |
| Repair Text: | From Oracle doc: Check return code in SERCERRNO. Make sure both sides of the connection are still running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9764 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmop: access error on oracle executable |
| Long Text: | The Mach driver could not access the Oracle executable. |
| Repair Text: | From Oracle doc: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9765 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmop: fork failed |
| Long Text: | The Mach driver could not fork the Oracle shadow process. |
| Repair Text: | From Oracle doc: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9766 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmop: buffer allocation failure. |
| Long Text: | The Mach driver failed to allocate enough virtual memory space for its I/O buffers. |
| Repair Text: | From Oracle doc: Decrease the value of BUFFER_SIZE parameter in the Two-Task driver host string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9767 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmfs: bad return code from msg_send. |
| Long Text: | The MSG_SEND system call failed while flushing the Mach driver's send buffer. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9768 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmgetmsg: could not read a message |
| Long Text: | The MSG_RECEIVE system call returned a failure code while waiting for a message in the Mach driver. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9769 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmbr: cannot send break message |
| Long Text: | The Mach driver could not send a break message to the Oracle shadow process break thread. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9770 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pws_look_up: translation failure. |
| Long Text: | The PWS_LOOK_UP routine failed to translate the name of the (Oracle helper) executable. |
| Repair Text: | From Oracle doc: Make sure ORACLE_SID and ORACLE_HOME are set and correct. Additional information gives the translation error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9771 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmwrtbrkmsg: bad return code from msg_send. |
| Long Text: | The MSG_SEND system call failed while sending a Mach driver break. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9772 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpmetbrkmsg: message from host had incorrect message type |
| Long Text: | The Mach driver received a message having an unrecognizable message type. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9773 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmgetdatmsg: message from host had incorrect message type |
| Long Text: | The Mach driver received a message having an unrecognizable message type. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9774 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmui: cannot send break message |
| Long Text: | The Mach driver could not send a break message to the Oracle shadow process break thread. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9775 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnmrs: reset protocol error |
| Long Text: | The Mach two-task driver could not reset the connection. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9776 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pws_look_up: access error on (Oracle helper) executable |
| Long Text: | The PWS_LOOK_UP call could not access the (Oracle helper) executable. |
| Repair Text: | From Oracle doc: Check the permissions on the (Oracle helper) executable and each component of the ORACLE_HOME/bin path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9777 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnpbr: cannot send break message |
| Long Text: | The pipe driver could not send a break message to the Oracle shadow process break thread. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9778 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snynfyport: failure allocating the notify port. |
| Long Text: | The routine failed to allocate or set the task's notify port. |
| Repair Text: | From Oracle doc: Possible operating system error. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9779 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snyGetPort: failure to allocate a port. |
| Long Text: | The PORT_ALLOCATE system call failed; system resources might be exhausted. |
| Repair Text: | From Oracle doc: Possible operating system error. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9786 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: open error, unable to open file. |
| Long Text: | Open system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9787 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: unrecognizable processing option, incorrect format. |
| Long Text: | Processing option passed is of incorrect format. |
| Repair Text: | From Oracle doc: Consult your IUG for permissible formats. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9788 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfrb: unable to read file. |
| Long Text: | Read system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. Verify file exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9789 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfsk: unable to read file. |
| Long Text: | Read system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. Verify file exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9790 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfcf: unable to close file. |
| Long Text: | Close system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9791 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slembdf: translation error, unable to translate error file name. |
| Long Text: | Additional information indicates error returned from SLTLN. |
| Repair Text: | From Oracle doc: Check additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9792 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sllfop: cannot allocate read buffer. |
| Long Text: | MALLOC system call returned an error. The system might have run out of heap space. |
| Repair Text: | From Oracle doc: Check additional information for the operating system error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9793 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szguns: length of user name is greater than buffer. |
| Long Text: | The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9794 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrbuild: length of role name is greater than buffer. |
| Long Text: | The length of the name of the role being looked up is longer than size of the buffer provided by the calling routine. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9795 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrbuild: malloc of role structure failed. |
| Long Text: | The allocation of memory for an internal structure used to hold a role descriptor failed. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9796 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | szrbuild: malloc of role name failed. |
| Long Text: | The allocation of memory for an internal buffer used to hold the name of a role failed. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9797 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Failed to get O/S MAC privileges. |
| Long Text: | The operating system would not allow the retrieval of this process' privileges. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9798 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Label comparison failed. |
| Long Text: | The comparison of two binary labels failed. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9799 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File label retrieval failed. |
| Long Text: | Oracle was unable to get a label attached to a file. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Process sensitivity label retrieval failed. |
| Long Text: | Oracle was unable to get the sensitivity label for a process. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get user ID from connection |
| Long Text: | Oracle was unable to retrieve the user's ID number from the SQL*Net connection. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Conversion of binary label to %s failed. |
| Long Text: | Oracle was unable to convert a binary label to a string. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Allocation of %s buffer failed. |
| Long Text: | a buffer used to hold the name of the file for which a label was to be obtained could not be allocated. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. The number of bytes that Oracle attempted to allocate is in the "Additional Information" field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Class conversion from binary to ORACLE failed. |
| Long Text: | Oracle was unable to convert a class component from binary format to Oracle format. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9805 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | conversion of category number to %s failed. |
| Long Text: | Oracle was unable to translate a category number to its corresponding string representation failed. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. The category number is contained in the "Additional information" field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9806 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Allocation of label %s buffer failed. |
| Long Text: | A temporary buffer used to hold a label could not be allocated. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. The number of bytes that Oracle attempted to allocate is in the "Additional Information" field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9807 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Conversion of label from %s to binary failed. |
| Long Text: | Oracle was unable to convert the string representation of a label to binary format. |
| Repair Text: | From Oracle doc: Re-enter a valid label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9808 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Could not obtain user clearance. |
| Long Text: | Oracle was unable to get a user's clearance level. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9809 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get user's group ID from connection |
| Long Text: | Oracle was unable to retrieve the user's group ID number from the SQL*Net connection. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get process ID from connection |
| Long Text: | Oracle was unable to retrieve the user's process ID number from the SQL*Net connection. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to initialize package. |
| Long Text: | Oracle was unable to initialize the library used to obtain security information. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get user clearance from connection |
| Long Text: | Oracle was unable to retrieve the user's operating system session clearance from the SQL*Net connection. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get directory status |
| Long Text: | Oracle was unable to determine if a directory is multilevel. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9814 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to expand file name |
| Long Text: | Oracle was unable to expand the name of a file that resides in multilevel directory. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9815 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File name buffer overflow |
| Long Text: | The buffer that Oracle uses to hold the expanded name of a too small. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to set effective privileges |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9817 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Write to audit file failed. |
| Long Text: | Oracle was unable to write an entry to the file used as the audit trail. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9818 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Number is too large |
| Long Text: | Oracle was unable to convert a component string to a number because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum. |
| Repair Text: | From Oracle doc: Correct the string and repeat the conversion. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9819 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Number exceeds maximum legal value |
| Long Text: | the number specified for a component was greater than the maximum value allowed for that component. |
| Repair Text: | From Oracle doc: Change the component to a value less than the maximum and repeat the conversion. The maximum component number is contained in the "Additional information" field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9820 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Conversion of class %s to numeric representation failed. |
| Long Text: | Oracle was unable to convert a class string to a number because all of the characters in the string were not numeric. |
| Repair Text: | From Oracle doc: Change the string to be either all numbers or all non-numeric characters and repeat the conversion. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9821 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Numeric label is not valid |
| Long Text: | A label specified in Oracle numeric format was found not to be valid. |
| Repair Text: | From Oracle doc: Re-enter a valid label. Consult your system's encodings for valid numeric component values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9822 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Translation of audit file name failed. |
| Long Text: | Oracle was unable to translate the value of the AUDIT_TRAIL_DEST initialization parameter. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9823 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device name is too long |
| Long Text: | The name of a device was too long to fit into an internal buffer. The additional information field contains the length of the device name. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9824 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to enable allowmacaccess privilege. |
| Long Text: | Oracle was not able to turn on ALLOWMACACCESS privilege so that it could do a label comparison. |
| Repair Text: | From Oracle doc: Check the UNIX error number. If it indicates that Oracle does not have the ALLOWMACACCESS privilege, add the ALLOWMACACCESS privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using CHPRIV (1M). If the executable already has the ALLOWMACACCESS privilege, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9825 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to disable allowmacaccess privilege. |
| Long Text: | Oracle was not able to turn off the ALLOWMACACCESS privilege after doing a label comparison. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9826 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SCLIN: cannot initialize atomic latch. |
| Long Text: | System call ATOMIC_OP() return error. |
| Repair Text: | From Oracle doc: Check additional information in the trace file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9827 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SCLGT: atomic latch return unknown error. |
| Long Text: | System call ATOMIC_OP() return unexpected error. |
| Repair Text: | From Oracle doc: Check additional information in the trace file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9828 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SCLFR: atomic latch return error. |
| Long Text: | System call ATOMIC_OP() return unexpected error. |
| Repair Text: | From Oracle doc: Check additional information in the trace file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9829 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pw_createPorts: server call pws_start_instance failed. |
| Long Text: | The call PWS_START_INSTANCE to (Oracle helper) failed; system resources might be exhausted. |
| Repair Text: | From Oracle doc: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9830 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snyAddPort: failed to perform a remote procedure call. |
| Long Text: | The MSG_RPC system call returned an error. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9831 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snyStartThread: failed to build the server port set. |
| Long Text: | The routine failed to build a port set on which to listen for requests. Possible operating system failure. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9832 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | infoCallback: bad message format. |
| Long Text: | The routine received an incorrectly formatted request. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9833 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | addCallback: bad message format. |
| Long Text: | The routine received an incorrectly formatted request. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9834 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snyGetPortSet: failed to collect info on a port. |
| Long Text: | The PORT_STATUS system called failed. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9835 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | addCallback: callback port is already in a set. |
| Long Text: | The port to be added to the callback list is already in a port set. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9836 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | addCallback: could not add a port to the callback set. |
| Long Text: | The PORT_SET_ADD system called failed. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9837 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | addCallback: could not add allocate a callback link. |
| Long Text: | The MALLOC library call failed to allocate space for a callback link. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9838 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | removeCallback: failure removing the callback port. |
| Long Text: | The port PORT_SET_REMOVE system call failed. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9839 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | removeCallback: callback port is not in the callback set. |
| Long Text: | The port to be removed to the callback list is not in the callback port set. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9840 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Name translation failure. |
| Long Text: | SLTLN() could not translate the named pipe ?/dbs/mon2arch_@. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9841 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Name translation failure. |
| Long Text: | SLTLN() could not translate the named pipe ?/dbs/arch2mon_@. |
| Repair Text: | From Oracle doc: Make sure that the ORACLE_HOME specified for this ORACLE_SID in ORATAB is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9842 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Archmon unable to create named pipe. |
| Long Text: | MKNOD() failed to create named pipe ?/dbs/mon2arch_@. |
| Repair Text: | From Oracle doc: Your current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only USERIDs in the DBA group of a given instance can run ARCHMON for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in ORATAB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9843 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Archmon unable to create named pipe. |
| Long Text: | MKNOD() failed to create named pipe ?/dbs/arch2mon_@. |
| Repair Text: | From Oracle doc: Your current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only USERIDs in the dba group of a given instance can run ARCHMON for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in ORATAB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9844 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Archmon unable to open named pipe. |
| Long Text: | OPEN() failed to open named pipe ?/dbs/mon2arch_@. |
| Repair Text: | From Oracle doc: Only the Oracle DBA can run ARCHMON. Make sure that your current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9845 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Archmon unable to open named pipe. |
| Long Text: | OPEN() failed to open named pipe ?/dbs/arch2mon_@. |
| Repair Text: | From Oracle doc: Only the Oracle DBA can run ARCHMON. Make sure that your current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9846 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: ARCH unable to open named pipe. |
| Long Text: | OPEN() failed to open named pipe ?/dbs/mon2arch_@. |
| Repair Text: | From Oracle doc: Make sure that the operating system USERID of the currently running database has search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9847 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: ARCH unable to open named pipe. |
| Long Text: | OPEN() failed to open named pipe ?/dbs/arch2mon_@. |
| Repair Text: | From Oracle doc: Make sure that the operating system USERID of the currently running database has search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9850 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Archmon unable to lock named pipe. |
| Long Text: | FCNTL() failed to set write lock on named pipe ?/dbs/arch2mon_@. |
| Repair Text: | From Oracle doc: Make sure that ARCHMON is not already active on another terminal for this ORACLE_SID. Only one ARCHMON session is allowed at a time for a given instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9851 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | soacon: Archmon unable to lock named pipe. |
| Long Text: | FCNTL() failed to set read lock on named pipe ?/dbs/mon2arch_@. |
| Repair Text: | From Oracle doc: Make sure that ARCHMON is not already active on another terminal for this ORACLE_SID. Only one ARCHMON session is allowed at a time for a given instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9853 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snyRemovePort: bad return code from request. |
| Long Text: | The request to remove a port from the callback set returned a failure code. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9854 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snyPortInfo: bad return code from request. |
| Long Text: | The request to collect information on a port in the callback set returned a failure code. Possible operating system error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9855 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | removeCallback: bad message format. |
| Long Text: | The routine received an incorrectly formatted request. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9856 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smpalo: vm_allocate error while allocating pga. |
| Long Text: | The VM_ALLOCATE system call returned an error. |
| Repair Text: | From Oracle doc: Check returned error. Possibly out of system resources. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9857 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | smprset: vm_protect error while protecting pga. |
| Long Text: | The VM_PROTECT system call returned an error. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9870 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spini: failure initializing maximum number of open files. |
| Long Text: | ULIMIT system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9871 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf. |
| Long Text: | Failure of sltln(?/tasdef@.dbf) while creating test and set pages. |
| Repair Text: | From Oracle doc: Check additional return error for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9872 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf. |
| Long Text: | CREATE() failed when trying to create the TASDEF file. |
| Repair Text: | From Oracle doc: Verify permissions on $(ORACLE_HOME)/dbs directory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9873 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TASDEF_OPEN: open error when opening tasdef@.dbf file. |
| Long Text: | Unable to open tasdef@.dbf file. |
| Repair Text: | From Oracle doc: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9874 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TASDEF_READ: read error, unable to read tasdef@.dbf file. |
| Long Text: | Read system call returned an error when attempting to read ?/dbs/tasdef@.dbf. |
| Repair Text: | From Oracle doc: Check errno returned. SGADEF file may be corrupted or incompatible with Oracle version. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9875 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file. |
| Long Text: | Write call failed. |
| Repair Text: | From Oracle doc: Check errno returned. Possibly out of space on device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9876 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file. |
| Long Text: | Close system call returned an error. |
| Repair Text: | From Oracle doc: Check errno returned. Possible operating system failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9877 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sstascre: shmget error, unable to get a shared memory segment. |
| Long Text: | Error in SHMGET. |
| Repair Text: | From Oracle doc: Check errno returned. Verify that enough shared memory is available on the system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9878 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sstascre/sstasat: shmat error, unable to attach tas write page |
| Long Text: | Error in SHMAT. |
| Repair Text: | From Oracle doc: Check errno returned.Verify that enough shared memory is available on the system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9879 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sstascre/sstasat: shmat error, unable to attach tas read page |
| Long Text: | Error in SHMAT. |
| Repair Text: | From Oracle doc: Check errno returned.Verify that enough shared memory is available on the system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9880 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sstasfre/sstasdel: shmdt error, unable to detach tas write page |
| Long Text: | Error in SHMDT. |
| Repair Text: | From Oracle doc: Check errno returned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9881 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sstasfre/sstasdel: shmdt error, unable to detach tas read page |
| Long Text: | Error in SHMDT. |
| Repair Text: | From Oracle doc: Check errno returned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9882 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sstasfre/sstasdel: shmctl error, unable to remove tas shm page |
| Long Text: | Error in SHMCTL. |
| Repair Text: | From Oracle doc: Check errno returned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9883 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Two Task interface: oratab file does not exist |
| Long Text: | The ORATAB file does not exist. |
| Repair Text: | From Oracle doc: Install Oracle before you use it or re-create the ORATAB file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9884 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Two Task interface: SID doens't match current PU |
| Long Text: | You are trying to start Oracle on another PU than you configured Oracle on or there is no entry for this SID in the ORATAB file. |
| Repair Text: | From Oracle doc: Start Oracle with this SID on its designated PU (see the ORATAB file). Or install the new database with SID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9885 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnTXtt: cannot create TXIPC channel |
| Long Text: | The TXIPC driver failed to create pipes for two-task communications with the Oracle shadow process. |
| Repair Text: | From Oracle doc: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9886 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnTXtt: translation error while expanding txipc@.trc. |
| Long Text: | Failure of sltln(txipc@.trc) while creating debug channel. |
| Repair Text: | From Oracle doc: Check additional return error for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9887 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnTXtt: Failed to create/open debug channel. |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9888 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnTXtt: txipc channel creation failed |
| Long Text: | The TXIPC driver failed to create channels for two-task communications with the Oracle shadow process. |
| Repair Text: | From Oracle doc: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9889 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnTXtt: access error on oracle executable |
| Long Text: | The TXIPC driver could not access the Oracle executable. |
| Repair Text: | From Oracle doc: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9890 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | osnTXtt: malloc failed |
| Long Text: | The TXIPX driver failed to allocate enough heap space for its context area buffers. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9908 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | slkmnm: gethostname returned error code. |
| Long Text: | The system call GETHOSTNAME returned an error. This is most likely an internal error. |
| Repair Text: | From Oracle doc: Make sure GETHOSTNAME is successful in other contexts, and if so contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9909 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Malloc of scratch buffer failed. |
| Long Text: | Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that Oracle attempted to allocate. |
| Repair Text: | From Oracle doc: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9910 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to find ORACLE password file entry for user. |
| Long Text: | No entry exists for the user in the Oracle password file. |
| Repair Text: | From Oracle doc: Have the database administrator install a password entry by running ORAPASSWD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9911 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Incorrect user password. |
| Long Text: | The password entered by the user was incorrect. |
| Repair Text: | From Oracle doc: Enter the correct password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9912 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Malloc of name buffer(s) failed. |
| Long Text: | Oracle was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users. |
| Repair Text: | From Oracle doc: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9913 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Malloc of dummy name failed. |
| Long Text: | Oracle was unable to allocate memory for the user name that is to be used in the encryption of the user's password. |
| Repair Text: | From Oracle doc: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9914 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to open the ORACLE password file. |
| Long Text: | Oracle could not open the password file for reading. |
| Repair Text: | From Oracle doc: Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running ORAPASSWD. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9915 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Password encryption failed. |
| Long Text: | Oracle was unable to encrypt a password. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9916 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Required password was not specified. |
| Long Text: | A user attempted to connect as "internal," but did not specify a password. |
| Repair Text: | From Oracle doc: Connect as internal again and specify a password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9918 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get user privileges from SQL*Net |
| Long Text: | Oracle was unable to retrieve the user's privilege set from the SQL*Net connection. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9919 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to set label of dedicated server |
| Long Text: | Oracle was unable to set the label of the dedicated to server to the required value. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also, check the privileges on the Oracle executable. It should have at least ALLOWMACACCESS privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9920 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get sensitivity label from connection |
| Long Text: | Oracle was unable to retrieve the user's sensitivity label from the SQL*Net connection. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9921 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get information label from connection |
| Long Text: | Oracle was unable to retrieve the user's information label from the SQL*Net connection. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9922 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Can't spawn process - background log directory not created properly |
| Long Text: | Oracle was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly. |
| Repair Text: | From Oracle doc: Examine the directory pointed to by the initialization parameter BACKGROUND_DUMP_DEST. Make sure that all of the following is true: The directory exists. The name indeed points to a directory, and is not a file. The directory is accessible and writable to the Oracle user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9923 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Can't spawn process - user log directory not created properly |
| Long Text: | Oracle was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly. |
| Repair Text: | From Oracle doc: Examine the directory pointed to by the initialization parameter USER_DUMP_DEST. Make sure that all of the following is true: The directory exists. The name indeed points to a directory, and is not a file. The directory is accessible and writable to the Oracle user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9924 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Can't spawn process - core dump directory not created properly |
| Long Text: | Oracle was unable to spawn a background process because the directory that holds the core dumps produced by Oracle processes in the event of exceptions was not created properly. |
| Repair Text: | From Oracle doc: Examine the directory pointed to by the initialization parameter CORE_DUMP_DEST. Make sure that all of the following is true: The directory exists. The name indeed points to a directory, and is not a file. The directory is accessible and writable to the Oracle user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9925 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to create audit trail file |
| Long Text: | Oracle was not able to create the file being used to hold audit trail records. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9926 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to set effective privilege set of the server |
| Long Text: | A dedicated server was unable to set it's own privilege set. |
| Repair Text: | From Oracle doc: Check the privileges granted to the Oracle executable. It must have at least ALLOWMACACESS privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9927 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to set label of server |
| Long Text: | Oracle was not able to set the label of a server to a new value. |
| Repair Text: | From Oracle doc: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has ALLOWMACACCESS privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9928 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to restore the label of server |
| Long Text: | Oracle was unable to restore the label of the server to the value that it had before raising it to database high. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9929 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GLB of two labels is invalid |
| Long Text: | The result of a greatest lower bound operation on two labels was not valid. |
| Repair Text: | From Oracle doc: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9930 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LUB of two labels is invalid |
| Long Text: | The result of a least upper bound operation on two labels was not valid. |
| Repair Text: | From Oracle doc: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9931 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to open ORACLE password file for reading |
| Long Text: | An attempt to open a password file for reading failed. |
| Repair Text: | From Oracle doc: Make sure that the permissions on the file have not been changed so that the Oracle user cannot open it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9932 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Close of ORACLE password file failed. |
| Long Text: | An attempt to close a password file failed. |
| Repair Text: | From Oracle doc: Check the UNIX error number for the specific reason. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9933 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Deletion of old password file failed. |
| Long Text: | The removal of the old password file failed. |
| Repair Text: | From Oracle doc: Check the UNIX error number for the specific reason. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9934 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Link of current password file to old failed. |
| Long Text: | Oracle was unable to create a link so that the old password file could be saved. |
| Repair Text: | From Oracle doc: Check the UNIX error number for the specific reason. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9935 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unlink of current password file failed. |
| Long Text: | Oracle was unable to complete the saving of the current password file. |
| Repair Text: | From Oracle doc: Check the UNIX error number for the specific reason. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9936 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Open of ORACLE password file for write failed. |
| Long Text: | Oracle was unable to create a password file. |
| Repair Text: | From Oracle doc: Check the UNIX error number for the specific reason. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9937 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Chmod of ORACLE password file failed. |
| Long Text: | Oracle was unable to change a password file to be read only. |
| Repair Text: | From Oracle doc: Check the UNIX error number for the specific reason. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9938 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Save of signal handlers failed. |
| Long Text: | Oracle was unable to save the previous values of selected signal handlers. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9939 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Restoration of signal handlers failed. |
| Long Text: | Oracle was unable to restore the previous values of selected signal handlers. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9940 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE password file header is corrupt |
| Long Text: | The header of one of the password files was not in the format that Oracle expected. |
| Repair Text: | From Oracle doc: Check the headers of both files. The header should be in the format "FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N" where N is a number. Remove the corrupt file(s) and re-run ORAPASSWD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9941 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Version of orapasswd or installer is older than file. |
| Long Text: | The version of ORAPASSWD or installer that is being run is older than that of the Oracle password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created. |
| Repair Text: | From Oracle doc: Run a version of the installer or ORAPASSWD whose version is the same or later than that of the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9942 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Write of ORACLE password file header failed. |
| Long Text: | The attempt to write out the header of the Oracle password file failed. |
| Repair Text: | From Oracle doc: Check the operating system error number. It is possible that the file system became full. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9943 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Allocation of memory for password list component failed. |
| Long Text: | When it is building a list of password file entries, Oracle allocates memory for various components. One of the allocations failed. |
| Repair Text: | From Oracle doc: Check the operating system error number. The system has probably run out of memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9944 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Password entry is corrupt. |
| Long Text: | An entry in an Oracle password file was not in the format that Oracle expected. |
| Repair Text: | From Oracle doc: Removed the corrupt file(s) and re-run ORAPASSWD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9945 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to initialize the audit trail file |
| Long Text: | Oracle was unable to write header information to the file being used as the audit trail. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9946 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File name too long for buffer |
| Long Text: | The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters. |
| Repair Text: | From Oracle doc: Use a shorter file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9947 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to allocate connection attributes structure |
| Long Text: | Oracle was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The "Additional Information" field holds the number of bytes that Oracle attempted to allocate. |
| Repair Text: | From Oracle doc: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9948 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Process information label retrieval failed. |
| Long Text: | Oracle was unable to get the information label for a process. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9949 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get client operating system privileges |
| Long Text: | Oracle was unable to get the operating system privileges for the client process. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9950 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to get server operating system privileges |
| Long Text: | Oracle was unable to get its privileges from the operating system. |
| Repair Text: | From Oracle doc: This is an error that should never happen. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9951 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to create file |
| Long Text: | Oracle was unable to create a file. |
| Repair Text: | From Oracle doc: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9952 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcmn: lk_open_convert unexpected return: open failed |
| Long Text: | The Distributed Lock Manager returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to the Distributed Lock Manager documentation or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9953 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scggc: unexpected return of a lock convert |
| Long Text: | The Distributed Lock Manager returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for Lock Manager error messages and refer to the Distributed Lock Manager documentation or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9954 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcc: unexpected return status to callback of lock close |
| Long Text: | The Distributed Lock Manager returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for Lock Manager error messages and refer to the Distributed Lock Manager documentation or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9955 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcan: unexpected return status when canceling a lock |
| Long Text: | DLM system service x returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message and refer to the Distributed Lock Manager documentation or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9956 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scgcm: unexpected lock status condition |
| Long Text: | A global locking system service returned an unexpected value. |
| Repair Text: | From Oracle doc: Check for system error message (if any) and refer to refer to the Distributed Lock Manager documentation or contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9957 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to send termination request to IMON |
| Long Text: | The attempt to send a termination signal to IMON failed. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9958 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IMON: two processes with the same ORACLE pid are active |
| Long Text: | The IMON process was unable to add an entry for a server process because another active process occupies the slot. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9959 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IMON: deletion of a process failed. |
| Long Text: | The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9960 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to establish signal handler for termination signal |
| Long Text: | Oracle was unable to set up a handler for the signal used to notify it that the instance was shutting down. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9961 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to restore termination signal handler |
| Long Text: | Oracle failed to set the handler for the termination signal to its previous value. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9962 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | lk_group_create error in scggrc |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9963 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | lk_group_attach error in scggra |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9964 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | lk_group_detach error in scggrd |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9966 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scumnt: translation error while expanding ?/dbs/lk |
| Long Text: | Failure of SLTLN in SCUMNT. |
| Repair Text: | From Oracle doc: Check additional returned error for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9967 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scumnt: unable to create or open file |
| Long Text: | Open system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9968 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scumnt: unable to lock file |
| Long Text: | Lock file operating system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9969 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scurls: unable to close lock file |
| Long Text: | Close system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9974 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfidini: Error Initializing SDI Channel |
| Long Text: | The process was unable to initialize the SDI channel properly. |
| Repair Text: | From Oracle doc: Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9975 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | kxfspini: Error Initializing SDI Process |
| Long Text: | The process was unable to attach to the SDI channel. |
| Repair Text: | From Oracle doc: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9976 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfqdini: Error Creating Port |
| Long Text: | The process was unable to create a communications endpoint. |
| Repair Text: | From Oracle doc: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9977 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfqhini: Error Connecting |
| Long Text: | The process was unable to connect to another endpoint. |
| Repair Text: | From Oracle doc: Verify that the SDI port specific limits correctly configured. Check that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9978 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfqhdel: Error Disconnecting from another endpoint. |
| Long Text: | The process was unable to disconnect cleanly from another endpoint. |
| Repair Text: | From Oracle doc: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9979 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfqhsnd: Error Sending a message to another endpoint |
| Long Text: | The process was unable to send a message to an existing endpoint. |
| Repair Text: | From Oracle doc: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9980 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfqdrcv: Error Receiving a message from another endpoint |
| Long Text: | The process encountered an error while trying to receive a message. |
| Repair Text: | From Oracle doc: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9981 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfqdreg: Error Adding a page to the SDI buffer pool |
| Long Text: | The process was unable to add a page to the SDI buffer pool. |
| Repair Text: | From Oracle doc: Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9982 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfqddrg: Error Removing a page from the SDI buffer pool |
| Long Text: | The process was unable to remove a page to the SDI buffer pool. |
| Repair Text: | From Oracle doc: Correct the operating system error and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9983 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skxfidsht: Error shutting down SDI channel |
| Long Text: | The process was unable to shut down the SDI channel. |
| Repair Text: | From Oracle doc: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9984 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist |
| Long Text: | File does not exist or is not accessible. |
| Repair Text: | From Oracle doc: Restart the instance to create the SGA definition file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9985 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SGA definition file could not be read |
| Long Text: | UNIX read() operation failed. |
| Repair Text: | From Oracle doc: Check errno and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9986 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong number of bytes read from SGA definition file |
| Long Text: | Struct SKGMSDEF size differs from the number of bytes read from the SGA file. |
| Repair Text: | From Oracle doc: Compare the two struct definitions and ensure that they are identical in size and structure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9987 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to attach to SGA in READ-ONLY mode |
| Long Text: | The instance is not up, or SGA segments are not read-accessible. |
| Repair Text: | From Oracle doc: Verify that the instance is up and read permissions for the SGA segments are set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9988 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while detaching SGA |
| Long Text: | SKGMSDEF struct is corrupted and/or segment addresses are modified. |
| Repair Text: | From Oracle doc: Safely shut down the instance and mount the SGA segments again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-9989 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to use invalid skgmsdef struct pointer |
| Long Text: | Pointer to SKGMSDEF struct used without validating it. |
| Repair Text: | From Oracle doc: Assign a valid address to the SKGMSDEF struct pointer before using it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-10000 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | %s |
| Long Text: | This event is sent when a message could not be properly mapped to EVENT:<set>-<num> due to a short text difference in the RtpLogOracle event catalogue. Please, check the details for event EVENT:<set>-<num> using RtpAdmCli or RTP GUI. |
| Repair Text: | From Oracle doc: The RtpLogOracle event catalogue should be updated to correspond the message issued by the OS to assure correct mapping. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a snapshot log already exists on table '%s' |
| Long Text: | An attempt was made to create a snapshot log on a table that already has a snapshot log. Each master table can have only one snapshot log. |
| Repair Text: | From Oracle doc: All snapshots on a table can use the same snapshot log for that table. To make changes to the existing log, use the ALTER SNAPSHOT LOG command or drop the snapshot log and create it again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create log: table '%s' already has a trigger |
| Long Text: | Snapshot logs are filled by a trigger on the master table. That trigger cannot be created. |
| Repair Text: | From Oracle doc: To create a snapshot log, drop the current trigger on the master. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | there is no snapshot log on table "%s"."%s" |
| Long Text: | There is no snapshot log on the master table. |
| Repair Text: | From Oracle doc: Create the log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" does not exist |
| Long Text: | The snapshot with the given owner and name does not exist. |
| Repair Text: | From Oracle doc: Verify inputs or create snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REFRESH FAST cannot be used for snapshot "%s"."%s" |
| Long Text: | The snapshot log does not exist or cannot be used. |
| Repair Text: | From Oracle doc: Use just REFRESH, which will reinstantiate the entire table. If a snapshot log exists and the form of the snapshot allows the use of a snapshot log, REFRESH FAST will be available starting the next time the snapshot is refreshed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | may not schedule automatic refresh for times in the past |
| Long Text: | An attempt was made to schedule an automated snapshot refresh for a time in the past. |
| Repair Text: | From Oracle doc: Choose a time in the future instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a snapshot with the same user.name already exists |
| Long Text: | An attempt was made to create a snapshot with the name of an existing snapshot. |
| Repair Text: | From Oracle doc: Create the snapshot using a different name or drop the existing snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot reuse parameters are inconsistent |
| Long Text: | The CREATE SNAPSHOT .. or CREATE SNAPSHOT LOG .. REUSE command was given inconsistent parameters immediately after the REUSE. |
| Repair Text: | From Oracle doc: Examine the other messages on the stack to find the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in snapshot refresh path |
| Long Text: | Table SNAP$_snapshot_name reads rows from the view MVIEW$_snapshot_name, which is a view on the master table (the master may be at a remote site). Any error in this path will cause this error at refresh time. For fast refreshes, the table master_owner.MLOG$_master is also referenced. |
| Repair Text: | From Oracle doc: Examine the other messages on the stack to find the problem. See if the objects SNAP$_snapshot_name, MVIEW$_snapshot_name, mowner.master@dblink, mowner.MLOG$_master@dblink still exist. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshots may not contain long columns |
| Long Text: | An attempt was made to create a snapshot with a long column. |
| Repair Text: | From Oracle doc: Do not attempt to create snapshot logs with long columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create snapshot log on table owned by SYS |
| Long Text: | CREATE SNAPSHOT LOG attempts to create a trigger on the table, but triggers cannot be created on SYS tables. |
| Repair Text: | From Oracle doc: Cannot create snapshot logs on SYS tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | execution of %s jobs failed |
| Long Text: | Some kind of error was caught in DBMS_IJOB.RUN. One or more jobs which were due to be run produced errors which they could not handle. |
| Repair Text: | From Oracle doc: Look at the alert log for details on which jobs failed and why. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error on auto execute of job %s |
| Long Text: | Some kind of error was caught while doing an automatic execute of a job. |
| Repair Text: | From Oracle doc: Look at the accompanying errors for details on why the execute failed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | updatable snapshots must be simple enough to do fast refresh |
| Long Text: | The updatable snapshot query has a join, subquery, union, connect by, order by, or group by. |
| Repair Text: | From Oracle doc: Make the snapshot simpler. If a join is really needed, make multiple simple snapshots then put a view on top of them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table '%s' does not contain a primary key constraint |
| Long Text: | The CREATE SNAPSHOT LOG command was issued with the WITH PRIMARY KEY option and the master table does not contain a primary key constraint or the constraint is disabled. |
| Repair Text: | From Oracle doc: Reissue the command using only the WITH ROWID option, create a primary key constraint on the master table, or enable an existing primary key constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a fast refresh snapshot from a complex query |
| Long Text: | Neither ROWIDs and nor primary key constraints are supported for complex queries. |
| Repair Text: | From Oracle doc: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot does not include all primary key columns |
| Long Text: | The query that instantiates the snapshot does not include all of the columns in the master's primary key constraint. |
| Repair Text: | From Oracle doc: Include all of the master's primary key columns in the snapshot query or create a ROWID snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot alter primary key snapshot '%s' to a rowid snapshot |
| Long Text: | Conversion of a primary key snapshot to a ROWID snapshot is not supported. |
| Repair Text: | From Oracle doc: Create a new snapshot or drop and re-create the snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | following error encountered during code generation for "%s"."%s" |
| Long Text: | The refresh operations for the indicated snapshot could not be regenerated due to errors. See following error text. |
| Repair Text: | From Oracle doc: Correct the indicated problem and repeat the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | master table is a synonym to a remote object |
| Long Text: | Snapshot of remote synonyms or snapshot logs on remote synonym are not supported. |
| Repair Text: | From Oracle doc: Do not create the snapshot or snapshot log on a remote synonym. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot %s is not registered |
| Long Text: | Attempt to unregister a snapshot that is not registered. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" is corrupt |
| Long Text: | The snapshot indicated is no longer valid. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot log on "%s"."%s" already has rowid |
| Long Text: | Snapshot log on the indicated table already has ROWID information. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing index on snapshot "%s"."%s" |
| Long Text: | The specified ROWID snapshot does not have the required index on the ROWID column of its underlying table. |
| Repair Text: | From Oracle doc: The snapshot is corrupted. Drop and re-create the snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot log on "%s"."%s" does not have primary key columns |
| Long Text: | Snapshot log on the indicated table does not have primary key information. |
| Repair Text: | From Oracle doc: Add primary keys to snapshot log using the alter snapshot command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot log on "%s"."%s" already has primary keys |
| Long Text: | Snapshot log on the indicated table already has primary key columns. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid filter column detected |
| Long Text: | One or more of the specified filter columns does not exist or is a primary key column. |
| Repair Text: | From Oracle doc: Ensure that all specified filter columns exist in the master table and ensure that primary key columns are not included in the list of filter columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dulicate filter column |
| Long Text: | One or more of the specified filter columns is already begin recorded in the snapshot log. |
| Repair Text: | From Oracle doc: Describe the snapshot log table and reissue the SQL command with specifying the filter columns that are already begin recorded in the snapshot log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot type is not supported by master site %s |
| Long Text: | Pre-Oracle8 master sites are not able to support primary key or subquery snapshots that are able to perform a fast refresh. |
| Repair Text: | From Oracle doc: Create a ROWID snapshot or use a master table from an Oracle8 site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOB columns may not be used as filter columns |
| Long Text: | LOB columns may not be used as filter columns. |
| Repair Text: | From Oracle doc: Remove LOB columns from the filter columns list and retry command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a fast refresh snapshot |
| Long Text: | The snapshot log does not exist or does not log the information needed by the snapshot to perform a fast refresh. |
| Repair Text: | From Oracle doc: Ensure that the snapshot log exists and logs the necessary information. For ROWID snapshots, the master table's ROWID must be logged. For primary key, snapshots the master table's primary key columns must be logged. For subquery snapshots filter, primary key, and ROWID values must all be logged. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use primary key columns from snapshot log on "%s"."%s" |
| Long Text: | The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time. |
| Repair Text: | From Oracle doc: A complete refresh is required before the next fast refresh. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use rowid column from snapshot log on "%s"."%s" |
| Long Text: | The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time. |
| Repair Text: | From Oracle doc: A complete refresh is required before the next fast refresh. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12033 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use filter columns from snapshot log on "%s"."%s" |
| Long Text: | The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time. |
| Repair Text: | From Oracle doc: A complete refresh is required before the next fast refresh. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12034 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot log on "%s"."%s" younger than last refresh |
| Long Text: | The snapshot log is younger than the last refresh. |
| Repair Text: | From Oracle doc: Perform a complete refresh of the snapshot before attempting another fast refresh. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not use snapshot log on "%s"."%s" |
| Long Text: | The snapshot log does not exist or cannot be used. |
| Repair Text: | From Oracle doc: Use just REFRESH, which will reinstantiate the entire table. If a snapshot log exists and the form of the snapshot allows the use of a snapshot log, REFRESH FAST will be available starting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | updatable snapshot log is not empty, refresh snapshot |
| Long Text: | The updatable snapshot log must be empty before an updatable ROWID snapshot can be altered to a primary key snapshot. |
| Repair Text: | From Oracle doc: Ensure that updatable snapshot log is empty by refreshing the snapshot before converting the updatable ROWID snapshot to a primary key snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown export format |
| Long Text: | An attempt was made to import a snapshot exported by an unknown export version (for example, from a newer release than the importing site) |
| Repair Text: | From Oracle doc: Re-export the file using a version of export known by the importing site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s literal has unexpected length |
| Long Text: | Corrupt or invalid information was detected during import of a snapshot. |
| Repair Text: | From Oracle doc: Ensure that the export log file has not been corrupted and that no errors were raised during export. Contact Oracle Customer Support if the problem persists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to use local rollback segment "%s" |
| Long Text: | A local rollback segment was specified in the CREATE SNAPSHOT command, but automatic refresh parameters were not specified. Therefore a refresh group was not created to automatically refresh the snapshot and the local rollback segment cannot be registered for future use. |
| Repair Text: | From Oracle doc: Either supply the automatic refresh parameters so that a refresh group will be created or do not specify a local rollback segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | master rollback segment option not support by master site %s |
| Long Text: | The master site of the current snapshot does not allow users to specify a rollback segment to be used for snapshot operations. This feature is only supported by Oracle8 or later master sites. |
| Repair Text: | From Oracle doc: Do not specify a master rollback segment in the current operation or choose a new master site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot record ROWIDs for index-organized table "%s"."%s" |
| Long Text: | Index-organized tables do not have ROWIDs. Therefore a snapshot log that records the ROWIDs of an index-organized table cannot be created. |
| Repair Text: | From Oracle doc: Do not include the WITH ROWID option when using the CREATE SNAPSHOT command and do not include the ADD ROWID option when using the ALTER SNAPSHOT command if the master table is index-organized. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot alter job_queue_processes in single process mode |
| Long Text: | There is no concept of detached processes in single process mode. Therefore altering the value of JOB_QUEUE_PROCESSES parameter is not allowed. |
| Repair Text: | From Oracle doc: Do not attempt to set JOB_QUEUE_PROCESSES in single process mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CREATE SNAPSHOT option |
| Long Text: | An invalid option was used in a CREATE SNAPSHOT statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CREATE SNAPSHOT LOG option |
| Long Text: | An invalid option was used in a CREATE SNAPSHOT LOG statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER SNAPSHOT LOG option |
| Long Text: | An invalid option was used in an ALTER SNAPSHOT LOG statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12051 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ON COMMIT attribute is incompatible with other options |
| Long Text: | The ON COMMIT refresh attribute is not allowed with other refresh options such as automatic periodic refresh. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot fast refresh materialized view %s.%s |
| Long Text: | This materialized view is not always fast refreshable. Either ROWIDs of certain tables are missing in the definition or the inner table of an outer join does not have UNIQUE constraints on join columns. |
| Repair Text: | From Oracle doc: Specify the FORCE or COMPLETE option. If this error occurred during creation, the materialized view definition could be changed. Refer to the documentation on materialized views. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot set the ON COMMIT refresh attribute for the materialized view |
| Long Text: | The materialized view does not satisfy conditions for refresh at commit time. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12056 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid REFRESH method |
| Long Text: | The NEVER REFRESH option may not be used under the following conditions: The snapshot is updatable The snapshot refreshes ON COMMIT Automatic refresh options are specified |
| Repair Text: | From Oracle doc: For updatable snapshots, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only snapshots, reissue the SQL command using ON DEMAND. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12057 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" is INVALID and must complete refresh |
| Long Text: | The status of the snapshot is INVALID and the snapshot may not be fast refreshed. |
| Repair Text: | From Oracle doc: Perform a complete refresh of the snapshot. Check the value of the STATUS column in DBA_SNAPSHOTS, ALL_SNAPSHOTS, or USER_SNAPSHOTS to verify that the snapshot is VALID after the complete refresh. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12058 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot cannot use prebuilt table |
| Long Text: | The snapshot cannot use the prebuilt table. |
| Repair Text: | From Oracle doc: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12059 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | prebuilt table "%s"."%s" does not exist |
| Long Text: | The specified prebuilt table does not exist. |
| Repair Text: | From Oracle doc: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | shape of prebuilt table does not match definition query |
| Long Text: | The number of columns or the type of a column in the prebuilt table does not match the snapshot definition query. |
| Repair Text: | From Oracle doc: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table matches the snapshot definition query. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER SNAPSHOT option |
| Long Text: | An invalid option was used in an ALTER SNAPSHOT statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12062 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction %s received out of sequence from site %s |
| Long Text: | A transaction from the client site was received out of sequence. This implies that one or more transactions are missing. |
| Repair Text: | From Oracle doc: Ensure that the transaction queue at the client site is valid and has not been corrupted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12063 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to apply transaction from site %s |
| Long Text: | The current transaction from the client site could not be applied to the master site. |
| Repair Text: | From Oracle doc: Ensure that the client site is still valid and that it has not been dropped from the master site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12064 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid refresh sequence number: %s |
| Long Text: | The client site is attempting to perform a refresh with an invalid refresh sequence. |
| Repair Text: | From Oracle doc: Perform a complete refresh to synchronize the refresh sequence number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12065 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown refresh group identifier %s |
| Long Text: | The specified refresh group does not exist at the master site. |
| Repair Text: | From Oracle doc: Ensure that the client site is still valid and that it has not been dropped from the master site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12066 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CREATE SNAPSHOT command |
| Long Text: | The Replication API does not support the following options and types of snapshot: ROWID snapshots REFRESH ON COMMIT ON PREBUILT TABLE BUILD DEFERRED NEVER REFRESH ENABLE QUERY REWRITE |
| Repair Text: | From Oracle doc: Create a PRIMARY KEY snapshot using REFRESH WITH PRIMARY KEY and/or remove the invalid options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12067 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | empty refresh groups are not allowed |
| Long Text: | The refresh group being instantiated does not contain any snapshots. |
| Repair Text: | From Oracle doc: Modify the template to include at least one snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12068 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | updatable snapshot log for snapshot "%s"."%s" does not exist |
| Long Text: | The updatable snapshot is missing the updatable snapshot log that is required to track updates made to the snapshot. |
| Repair Text: | From Oracle doc: Create the updatable snapshot log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12069 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid object for offline instantiation |
| Long Text: | Only snapshots can be offline instantiated. The object being offline instantiated is not a valid snapshot. |
| Repair Text: | From Oracle doc: Remove the object from the template or replace the object with a valid snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12070 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot offline instantiate snapshot "%s"."%s" |
| Long Text: | Offline instantiation does not support snapshots using the following options: ON PREBUILT TABLE BUILD DEFERRED |
| Repair Text: | From Oracle doc: Remove the invalid options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | definition query of "%s"."%s" is invalid for offline instantiation |
| Long Text: | Offline instantiation requires snapshot definition queries to observe the following constraints: "SELECT *" may not be used. The query must explicitly specify each column in the select list. The database link that will be used by the snapshot site to connect to the master site must be included with each master table referenced in the query. All master tables referenced must be located at the local site. References to other sites are not allowed. |
| Repair Text: | From Oracle doc: Modify the snapshot definition query. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12072 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | updatable materialized view log data for '%s'.'%s' cannot be created |
| Long Text: | The updatable materialized view is missing the updatable materialized view log that is required to track updates made to the materialized view. |
| Repair Text: | From Oracle doc: Create the updatable materialized view log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12073 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | request cannot be processed |
| Long Text: | An out-of-sequence request was made and it cannot be processed. |
| Repair Text: | From Oracle doc: Try again with a valid request. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid memory address |
| Long Text: | An attempt was made to access an invalid memory region. |
| Repair Text: | From Oracle doc: Reconnect and try the command again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12075 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid object or field |
| Long Text: | ] An attempt was made to access an invalid field or object in the Java Virtual Memory. |
| Repair Text: | From Oracle doc: Retry the request. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12076 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid threshold value |
| Long Text: | The result set threshold or LOB threshold value is not supported. |
| Repair Text: | From Oracle doc: Specify a threshold value below 64K. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12077 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | temporary updatable materialized view log does not exist |
| Long Text: | Temporary updatable materialized view log was not created or was dropped. |
| Repair Text: | From Oracle doc: Re-create the temporary updatable materialized view log. Warning: This will cause a complete refresh of the materialized view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fast refresh of refresh group ID %s failed |
| Long Text: | Refresh result set sent through client method REFRESH_REQ_RESULT returns an unknown value. |
| Repair Text: | From Oracle doc: Re-issue the refresh request. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12079 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot options require COMPATIBLE parameter to be %s or greater |
| Long Text: | The following snapshot options require 8.1 or higher compatibility setting: ON COMMIT ON PREBUILT TABLE BUILD DEFERRED NEVER REFRESH ENABLE QUERY REWRITE |
| Repair Text: | From Oracle doc: Shut down and restart with an appropriate compatibility setting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12081 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | , 00000 update operation not allowed on table %s.%s |
| Long Text: | An attempt was made to update a read-only materialized view. Only Oracle is allowed to update a read-only materialized view. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s'.'%s' cannot be index organized |
| Long Text: | An attempt was made to create an index-organized materialized aggregate view or an index-organized updatable ROWID materialized view. This is not supported. |
| Repair Text: | From Oracle doc: Try to create the materialized view without the index organization clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12083 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must use DROP MATERIALIZED VIEW to drop %s.%s |
| Long Text: | An attempt was made to drop a materialized view using a command other than DROP MATERIALIZED VIEW. |
| Repair Text: | From Oracle doc: Use the DROP MATERIALIZED VIEW command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must use ALTER MATERIALIZED VIEW to alter %s.%s |
| Long Text: | An attempt was made to alter a materialized view using a command other than ALTER MATERIALIZED VIEW. |
| Repair Text: | From Oracle doc: Use the ALTER MATERIALIZED VIEW command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:unable to send data |
| Long Text: | Unable to send data. Connection probably disconnected. |
| Repair Text: | From Oracle doc: Re-establish connection. If the error is persistent, turn on tracing and reexecute the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12151 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | TNS:received bad packet type from network layer |
| Long Text: | Internal error. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:unable to send break message |
| Long Text: | Unable to send break message. Connection probably disconnected. |
| Repair Text: | From Oracle doc: Re-establish connection. If the error is persistent, turn on tracing and reexecute the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:not connected |
| Long Text: | Not currently connected to a remote host. |
| Repair Text: | From Oracle doc: Re-establish connection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12154 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:could not resolve service name |
| Long Text: | The service name specified is not defined correctly in the TNSNAMES.ORA file. |
| Repair Text: | From Oracle doc: Make the following checks and correct the error: - Verify that a TNSNAMES.ORA file exists and is in the proper place and accessible. See the operating system specific manual for details on the required name and location. - Check to see that the service name exists in one of the TNSNAMES.ORA files and add it if necessary. - Make sure there are no syntax errors anywhere in the file. Particularly look for unmatched parentheses or stray characters. Any error in a TNSNAMES.ORA file makes it unusable. See Chapter 4 in the SQL*Net V2 Administrator's Guide. If possible, regenerate the configuration files using the Oracle Network Manager. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:received bad datatype in NSWMARKER packet |
| Long Text: | Internal error during break handling. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12156 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:tried to reset line from incorrect state |
| Long Text: | Internal error during break handling. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12157 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:internal network communication error |
| Long Text: | Internal error during network communication. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12158 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:could not initialize parameter subsystem |
| Long Text: | Unable to locate parameter file. |
| Repair Text: | From Oracle doc: Verify that a valid parameter file exists, and is readable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12159 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:trace file not writeable |
| Long Text: | The trace file to be generated is not writeable by this user. |
| Repair Text: | From Oracle doc: If the user does not have write permissions in the directory to which the trace file will be written, contact the DBA to get the proper permissions or use TRACE_DIRECTORY_CLIENT in SQLNET.ORA to specify a directory the user can write to. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:internal error: Bad error number |
| Long Text: | Corrupt error reporting subsystem. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:internal error: partial data received |
| Long Text: | The connection may be terminated. |
| Repair Text: | From Oracle doc: Reconnect and try again. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:service name is incorrectly specified |
| Long Text: | The connect descriptor corresponding to the service name in TNSNAMES.ORA is incorrectly specified. |
| Repair Text: | From Oracle doc: Make sure there are no syntax errors in the connect descriptor. Particularly look for unmatched parentheses or stray characters. Any error in a TNSNAMES.ORA file makes it unusable. See Chapter 4 in the SQL*Net V2 Administrator's Guide. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:connect descriptor is too long |
| Long Text: | The connect descriptor corresponding to the service name in TNSNAMES.ORA is too long. |
| Repair Text: | From Oracle doc: The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded. Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12164 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:Sqlnet.fdf file not present |
| Long Text: | The sqlnet.fdf file doesn't exist in $ORACLE_HOME/network/admin. |
| Repair Text: | From Oracle doc: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your ORA file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12165 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:Trying to write trace file into swap space. |
| Long Text: | Oracle Trace doesn't allow writing trace information into your swap space. |
| Repair Text: | From Oracle doc: Oracle Trace cannot write trace information into swap space so either disable tracing or redirect trace files to be written to another area of your disk. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12196 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:received an error from TNS |
| Long Text: | The navigation layer received an error from TNS. |
| Repair Text: | From Oracle doc: See the error log file for the specific TNS error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12197 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:keyword-value resolution error |
| Long Text: | The navigation layer received an error while trying to look up a value for a keyword. |
| Repair Text: | From Oracle doc: Check the syntax of the connect descriptor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12198 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:could not find path to destination |
| Long Text: | Could not navigate a path through Interchanges to the destination. This error occurs if an invalid community is in the address string, or the address includes a protocol that is not available or the TNSNAV.ORA file does not have a correct CMANAGER address specified or the Interchange is down. |
| Repair Text: | From Oracle doc: Assure that Interchanges necessary to get to the desired destination are up and have available capacity for an additional connection. Also check that the correct community and protocol have been specified in the CMANAGER address used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:could not allocate memory |
| Long Text: | Out of memory on machine. |
| Repair Text: | From Oracle doc: Reconfigure machine to have more storage or run fewer applications while the Interchange is running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:encountered too small a connection buffer |
| Long Text: | TNS connection buffer supplied by the application was too small to retrieve the data sent back. |
| Repair Text: | From Oracle doc: Supply a larger connection buffer. If problem persists, call Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:internal navigation error |
| Long Text: | Internal navigation error. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:unable to connect to destination |
| Long Text: | Invalid TNS address supplied or destination is not listening. This error can also occur because of underlying network transport problems. |
| Repair Text: | From Oracle doc: Verify that the service name you entered on the command line was correct. Ensure that the listener is running at the remote node and that the ADDRESS parameters specified in TNSNAMES.ORA are correct. Finally, check that all Interchanges needed to make the connection are up and running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS: received data refused from an application |
| Long Text: | The application using the Interchange or Connection Manager refused the connection at the listener. |
| Repair Text: | From Oracle doc: Make sure that the application listener at the destination is functioning correctly. If it is and the problem persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:could not get failed addresses |
| Long Text: | Internal navigation error. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:received a TNS error during navigation |
| Long Text: | Internal navigation error because of an unexpected TNS error. |
| Repair Text: | From Oracle doc: Look at the log file to find the TNS error. If necessary, turn on tracing and repeat the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:unable to perform navigation |
| Long Text: | Improperly configured navigation file TNSNAV.ORA. |
| Repair Text: | From Oracle doc: Check the syntax of the TNSNAV.ORA file on the application`s machine, and verify that it lists the correct communities. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:could not find the TNSNAV.ORA file |
| Long Text: | Either the ORACLE environment is not set up correctly, or the TNSNAV.ORA file is not present. |
| Repair Text: | From Oracle doc: Ensure that the ORACLE environment is set up appropriately on your platform and that a TNSNAV.ORA file is present. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:encountered uninitialized global |
| Long Text: | Application calling navigation routine has not properly configured the global variables. There are no TNSNAV.ORA files available, or they are defective. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:error in finding Navigator data |
| Long Text: | Application calling navigation routine has not properly configured the TNSNAV.ORA file. |
| Repair Text: | From Oracle doc: Check the syntax of the TNSNAV.ORA file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA |
| Long Text: | TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined. |
| Repair Text: | From Oracle doc: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA |
| Long Text: | The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file does not have a CMANAGER_NAME specified. |
| Repair Text: | From Oracle doc: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS binding. Use of the Oracle Network Manager should eliminate this error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA |
| Long Text: | The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file does not have an ADDRESS specified. |
| Repair Text: | From Oracle doc: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:missing local communities entry in TNSNAV.ORA |
| Long Text: | There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA. |
| Repair Text: | From Oracle doc: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA |
| Long Text: | Address binding for PREFERRED_NAVIGATORS entry is improperly entered. entry. |
| Repair Text: | From Oracle doc: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA |
| Long Text: | Address binding for the PREFERRED_CMANAGERS entry in the client's TNSNAV.ORA file is improperly entered. |
| Repair Text: | From Oracle doc: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA |
| Long Text: | There is a syntax error in the PREFERRED_CMANAGERS entry, or addresses specified are wrong, or the intended Connection Managers are unavailable. |
| Repair Text: | From Oracle doc: Check the PREFERRED_CMANAGERS entries in the client's TNSNAV.ORA file and correct them or talk with your network administrator to determine if the specified Connection Managers are available. Verify that the Interchanges are active by using the INTCTL STATUS command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:unacceptable network configuration data |
| Long Text: | Poorly formed network configuration data. For example, a PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the client's TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA. |
| Repair Text: | From Oracle doc: Check the entries in TNSNAV.ORA and the Interchange configuration files and correct them. If necessary, talk with your network administrator to determine if the specified Interchanges (Connection Managers) are available and properly configured. Use the Oracle Network Manager to generate the configuration files if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:missing community name from address in ADDRESS_LIST |
| Long Text: | This error occurs when an ADDRESS_LIST has some ADDRESSes in it that have no COMMUNITY component and others that do have a COMMUNITY component. |
| Repair Text: | From Oracle doc: Check that in the connect descriptors you are using either all the ADDRESSes have a COMMUNITY component or all do not. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12221 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:illegal ADDRESS parameters |
| Long Text: | An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport. |
| Repair Text: | From Oracle doc: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12222 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no such protocol adapter |
| Long Text: | The protocol adapter requested (by way of the "(PROTOCOL=..)" keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adaptor is not installed. |
| Repair Text: | From Oracle doc: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12223 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:internal limit restriction exceeded |
| Long Text: | Too many TNS connections open simultaneously. |
| Repair Text: | From Oracle doc: Wait for connections to close and re-try. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12224 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no listener |
| Long Text: | The connection request could not be completed because the listener is not running. |
| Repair Text: | From Oracle doc: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12225 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:destination host unreachable |
| Long Text: | Contact can not be made with remote party. |
| Repair Text: | From Oracle doc: Make sure the network driver is functioning and the network is up. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12226 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operating system resource quota exceeded |
| Long Text: | The current user has exceeded the allotted resource assigned in the operating system. |
| Repair Text: | From Oracle doc: Acquire more operating system resource, or perform a different function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12227 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:syntax error |
| Long Text: | The supplied connect descriptor contains illegal syntax. |
| Repair Text: | From Oracle doc: Check the syntax of the connect descriptor in TNSNAMES.ORA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12228 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:protocol adapter not loadable |
| Long Text: | On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned. |
| Repair Text: | From Oracle doc: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12229 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:Interchange has no more free connections |
| Long Text: | One or more Interchanges along the path to the destination desired has no more free connections available to be used for this call. |
| Repair Text: | From Oracle doc: Try again later when the Interchanges are less busy, or contact your network administrator to have him determine which interchange it is, and increase the number of connections available on that interchange. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:Severe Network error occurred in making this connection |
| Long Text: | This error is reported by an interchange which fails to make contact with the destination due to a physical network error while calling a destination. |
| Repair Text: | From Oracle doc: Try again later when the network service may have been fixed or report the problem to your Network Administrator so that he may fix the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:No connection possible to destination |
| Long Text: | This error is reported by an interchange which fails to find a possible connection along the path to the destination. |
| Repair Text: | From Oracle doc: Report the problem to your Network Administrator so that he may fix the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:No path available to destination |
| Long Text: | This error is reported by an interchange which fails to find a possible path to the destination. |
| Repair Text: | From Oracle doc: Report the problem to your Network Administrator so that he may fix the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:Failure to accept a connection |
| Long Text: | This error is reported by an interchange which fails to accept a connection due to a redirect failure. |
| Repair Text: | From Oracle doc: Report the problem to your Network Administrator so that he may isolate the interchange problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:Redirect to destination |
| Long Text: | This error is reported by an interchange which determines that this interchange is not the right gateway and needs to redirect the connection to another gateway along the path to the destination. |
| Repair Text: | From Oracle doc: None. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:Failure to redirect to destination |
| Long Text: | This error is reported by an interchange which fails to redirect a connection to another interchange along the path to the destination. |
| Repair Text: | From Oracle doc: Report the problem to your Network Administrator so that he may fix the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12236 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:protocol adapter not loaded |
| Long Text: | On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned. |
| Repair Text: | From Oracle doc: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link type is invalid for the ALTER DATABASE statement |
| Long Text: | The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database. |
| Repair Text: | From Oracle doc: Re-issue the ALTER DATABASE statement using a valid ROM: link to the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See your documentation for Oracle security-related products for more information about creating database links using the ROM: link type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in database link's connect %s |
| Long Text: | The connect string in the CREATE DATABASE LINK statement has a syntactical error. |
| Repair Text: | From Oracle doc: Drop the database link and re-create it using valid syntax. See Oracle8i SQL Reference for more information about the connect string portion of the CREATE DATABASE LINK statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logon to database (link name %s) denied |
| Long Text: | There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the secondary database are not identical to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, you can get this error if the username/password combination specified in the connect string of the database link definition is invalid (either not created or has an invalid password). |
| Repair Text: | From Oracle doc: In the first case, ensure that the secondary database contains a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In general, you should always use operating system authentication in Trusted Oracle (see the your documentation for Oracle security-related products for more information about the advantages of operating system authentication). In the second case, ensure that your username in the secondary database has been created. In the third case, ensure that the username specified in the connect string has been created in the secondary database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database (link name %s) is already mounted |
| Long Text: | You are attempting to mount a secondary database that has already been mounted by your instance. |
| Repair Text: | From Oracle doc: The database is already mounted, so you need not take additional action to mount it. To establish access, use the ALTER DATABASE linkname OPEN command to open the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database (link name %s) is already open |
| Long Text: | You are attempting to open a secondary database that is already open. |
| Repair Text: | From Oracle doc: The database is open and you need not take additional action to establish access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database (link name %s) is not open and AUTO_MOUNTING=FALSE |
| Long Text: | The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled. |
| Repair Text: | From Oracle doc: Manually mount and open the secondary database using ALTER DATABASE linkname with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to mount database (link name %s) |
| Long Text: | This message should be accompanied by additional error messages that indicate the cause of the problem. |
| Repair Text: | From Oracle doc: Follow the steps outlined in the accompanying error messages to resolve the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12323 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to open database (link name %s) |
| Long Text: | This message should be accompanied by additional error messages that indicate the cause of the problem. |
| Repair Text: | From Oracle doc: Follow the steps outlined in the accompanying error messages to resolve the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12324 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use the ROM: link type on a private database link |
| Long Text: | You can only specify the ROM: link type on a public, not a private, database link. |
| Repair Text: | From Oracle doc: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12326 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database %s is closing immediately; no operations are permitted |
| Long Text: | The database you attempted to access is closing, so your operation has been terminated. |
| Repair Text: | From Oracle doc: Wait until the database has been reopened, or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12329 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database %s is closed; no operations are permitted |
| Long Text: | The database you attempted to access is closed, so your operation has been terminated. |
| Repair Text: | From Oracle doc: Wait until the database is reopened, or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12333 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database (link name %s) is not mounted |
| Long Text: | An attempt was made to open a database that has not been mounted. |
| Repair Text: | From Oracle doc: Mount the database with the ALTER DATABASE linkname MOUNT command, then re-attempt to open the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12334 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database (link name %s) is still open |
| Long Text: | An attempt was made to dismount a database that is still open. |
| Repair Text: | From Oracle doc: Close the database with the ALTER DATABASE linkname CLOSE command, then re-attempt to dismount the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database (link name %s) is not open |
| Long Text: | An attempt was made to close a database that is not open. |
| Repair Text: | From Oracle doc: The database is closed; you can proceed with dismounting it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12336 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot login to database (link name %s) |
| Long Text: | An attempt was made to login while another user is mounting or dismounting the same database. |
| Repair Text: | From Oracle doc: Check to see if the database is in the middle of being mounted or opened and try your login again once the database is accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of open mounts exceeded |
| Long Text: | The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255). |
| Repair Text: | From Oracle doc: Change the value of this parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | open mounts exceeds limit set on the OPEN_MOUNTS parameter |
| Long Text: | The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter. |
| Repair Text: | From Oracle doc: Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user %s lacks CREATE SESSION privilege in database link (linkname %s) |
| Long Text: | There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege. |
| Repair Text: | From Oracle doc: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link being dropped is still mounted |
| Long Text: | An attempt was made to drop a ROM: database link that was still mounted and/or opened. |
| Repair Text: | From Oracle doc: Close and dismount the database and then re-issue the drop statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create view using a remote object which has a remote object reference |
| Long Text: | An attempt was made to create a view which references a remote object which, in turn, references an object on another database. Since the view that would have been created references a remote object, that object cannot reference an object on another database. |
| Repair Text: | From Oracle doc: Choose a different object to reference in your view or change the remote object so that it does not reference another database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s.%s@%s is invalid |
| Long Text: | An attempt was made to reference (compile against) an object of a secondary database but the object is invalid and the system cannot validate or recompile it because it is in a secondary database. |
| Repair Text: | From Oracle doc: Manually recompile the invalid object in the secondary database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | secondary stored object cannot reference remote object |
| Long Text: | An attempt was made to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done. |
| Repair Text: | From Oracle doc: Choose a different object to reference or change the remote view or procedure so that it does not reference another database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | secondary object being dropped |
| Long Text: | An attempt was made to access a object (for example, a table or view) on a secondary database that was in the process of being dropped. |
| Repair Text: | From Oracle doc: Repeat the operation. If you receive this message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBLOW is not a valid operating system label |
| Long Text: | The operating system label corresponding to DBLOW has become invalid due to a change in operating system label definitions. |
| Repair Text: | From Oracle doc: Use the operating system facilities to restore the definition of this label, or change the value of DBLOW to a valid label. To change the value of DBLOW, you must mount the database and switch to OSMAC mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBHIGH is not a valid operating system label |
| Long Text: | The operating system label corresponding to DBHIGH has become invalid due to a change in operating system label definitions. |
| Repair Text: | From Oracle doc: Use the operating system facilities to restore the definition of this label, or change the value of DBHIGH to a valid label. To change the value of DBHIGH, you must mount the database and switch to OSMAC mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file: %s |
| Long Text: | Reporting file name for detail of another message. |
| Repair Text: | From Oracle doc: Examine the message stack for additional detail. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file label (%s) must be equal to DBHIGH (%s) |
| Long Text: | An Oracle file was found to have a label that does not match the operating system equivalent of DBHIGH. This may be caused if DBHIGH has been changed, or if the file has been relabeled. |
| Repair Text: | From Oracle doc: Either relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device low (%s) must be dominated by DBLOW (%s) |
| Long Text: | A Oracle file was found on a device with an authorized range insufficient to handle the lowest labeled data in the file. DBLOW must always dominate the minimum device label. |
| Repair Text: | From Oracle doc: Lower the authorized minimum device label or move the file to a different device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12405 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device high (%s) must dominate DBHIGH (%s) |
| Long Text: | An Oracle file was found on a device with an authorized range insufficient to handle the highest labeled data in the file. DBHIGH must always be dominated by the maximum device label. |
| Repair Text: | From Oracle doc: Raise the authorized maximum device label or move the file to a different device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must be at DBHIGH (%s) in OS to add files to a tablespace |
| Long Text: | A file was added to a new or existing tablespace by a user whose operating system label was not equal to DBHIGH. |
| Repair Text: | From Oracle doc: Log in to the operating system at DBHIGH to add the file. If you are creating a new tablespace, set your session label to the label at which you want the tablespace to be created, then create the tablespace. If you are adding a file to an existing tablespace, set your session label to match the creation label of the tablespace, then alter the tablespace See the your documentation for Oracle security-related products for more detailed information about creating and altering tablespaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot insert or update the ROWLABEL column of a view |
| Long Text: | An attempt was made to insert into or update the ROWLABEL column of a view. Trusted Oracle does not allow you to modify the ROWLABEL column of a view. |
| Repair Text: | From Oracle doc: While you cannot modify the ROWLABEL column of a view, you can modify the ROWLABEL column in the base table(s) of the view. Use the INSERT or UPDATE commands to modify the base tables(s); consequently, this modifies the view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace previously existed at another label (%s) |
| Long Text: | A tablespace by this name was previously created and dropped at another label. Part of the dictionary entry for the old tablespace remains, and the new tablespace is attempting to reuse the old entry. |
| Repair Text: | From Oracle doc: Either re-create the tablespace at the original label or choose a new name for this tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12409 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBLOW cannot be null in DBMS MAC mode |
| Long Text: | The database was started in DBMS MAC mode before resetting DBLOW. |
| Repair Text: | From Oracle doc: Restart the database in OS MAC mode and supply valid values for both DBHIGH and DBLOW before starting up in DBMS MAC mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12410 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBHIGH cannot be null in DBMS MAC mode |
| Long Text: | The database was started in DBMS MAC mode before resetting DBHIGH. |
| Repair Text: | From Oracle doc: Restart the database in OS MAC mode and supply valid values for both DBHIGH and DBLOW before starting up in DBMS MAC mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12411 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBHIGH must dominate DBLOW |
| Long Text: | DBHIGH does not dominate DBLOW. |
| Repair Text: | From Oracle doc: Restart the database in OS MAC mode and supply valid values for DBHIGH and DBLOW before starting up in DBMS MAC mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12412 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot raise DBLOW above %s |
| Long Text: | You tried raise DBLOW above its current value. DBLOW can only be lowered; it cannot be raised. |
| Repair Text: | From Oracle doc: Do not attempt to raise DBLOW. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12413 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot lower DBHIGH below %s |
| Long Text: | An attempt was made to lower DBHIGH below its current value. DBHIGH can only be raised. |
| Repair Text: | From Oracle doc: Do not attempt to lower DBHIGH. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12414 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must be DBHIGH (%s) to startup database |
| Long Text: | An attempt was made to open a database while at an operating system label not equal to DBHIGH. |
| Repair Text: | From Oracle doc: Login at DBHIGH to start the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12415 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session label must dominate the creation label of role %s |
| Long Text: | An attempt was made to grant a privilege to a role while at a label that does not dominate the role's creation label. Your DBMS label must dominate the role's creation label in order to grant a privilege to the role. |
| Repair Text: | From Oracle doc: Check the creation label of the role and perform the grant while at a label that dominates the creation label of the role. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12416 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of audit must dominate user |
| Long Text: | An attempt was made to set statement audit options for a user while at a label that does not dominate the user's creation label. Your DBMS label must dominate the user's creation label in order to set statement audit options for the user. |
| Repair Text: | From Oracle doc: Check the creation label of the user and set the statement audit option while at a label that dominates the creation label of the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12418 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of index must equal table |
| Long Text: | An attempt was made to create an index on a table while at a label that does not match the table's creation label. Your DBMS label must match the table's creation label in order to create an index on the table. If the table was created at DBHIGH or DBLOW, your label must be set to DBHIGH or DBLOW. |
| Repair Text: | From Oracle doc: Check the creation label of the table and create the index while at a label that matches the creation label of the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12419 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of column must equal table |
| Long Text: | An attempt was made to add a column to a table while at a label that does not match the table's creation label. Your DBMS label must match the table's creation label in order to add a column to the table. |
| Repair Text: | From Oracle doc: Check the creation label of the table and add the column while at a label that matches the creation label of the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12420 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of stored object must dominate referenced object %s |
| Long Text: | An attempt was made to create or you issued a statement that tried to create a stored object (view, procedure, function, trigger) which references some object while at a label that does not dominate the referenced object's creation label. Your DBMS label must dominate the creation labels of all referenced objects in order to create a stored object. While the referenced object may be visible due to enabled MAC privileges, MAC privileges cannot be used to create the stored object. |
| Repair Text: | From Oracle doc: Check the creation labels of the referenced objects and create the stored object while at a label that dominates the creation labels of all referenced objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12421 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of grant must dominate object |
| Long Text: | An attempt was made to grant privileges on an object while at a label that does not dominate the object's creation label. Your DBMS label must dominate the object's creation label in order to grant privileges on the object. |
| Repair Text: | From Oracle doc: Check the creation label of the object and perform the grant while at a label that dominates the creation label of the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12422 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of grant must dominate grantee %s |
| Long Text: | An attempt was made to grant privileges to a user while at a label that does not dominate the user's creation label. Your DBMS label must dominate the user's creation label in order to grant privileges to the user. |
| Repair Text: | From Oracle doc: Check the creation label of the user and grant the privileges while at a label that dominates the creation label of the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12423 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of constraint must equal table |
| Long Text: | An attempt was made to add a constraint to a table while at a label that does not match the table's creation label. Your DBMS label must match the creation label of the table in order to add a constraint to the table. |
| Repair Text: | From Oracle doc: Check the creation label of the table and add the constraint while at a label that matches the creation label of the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12424 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of object must dominate tablespace |
| Long Text: | An attempt was made to create an object in a tablespace while at a label that does not dominate the tablespace's creation label. Your DBMS label must dominate the tablespace's creation label in order to create an object in the tablespace. |
| Repair Text: | From Oracle doc: Check the creation label of the tablespace and create the object while at a label that dominates the creation label of the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12425 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of table must dominate cluster |
| Long Text: | An attempt was made to create a table in a cluster while at a label that does not dominate the cluster's creation label. Your DBMS label must dominate the cluster's creation label in order to create a table in the cluster. |
| Repair Text: | From Oracle doc: Check the creation label of the cluster and create the table while at a label that dominates the creation label of the cluster. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12426 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of user must dominate default or temporary tablespace |
| Long Text: | An attempt was made to assign a user a default or temporary tablespace when the user's creation label did not dominate the tablespace's creation label. The user's creation label must dominate the tablespace's creation label in order for the default or temporary tablespace to be assigned to the user. Your DBMS label must dominate both the user's and the tablespace's creation labels in order to assign the tablespace to the user. |
| Repair Text: | From Oracle doc: Check the creation label of the default or temporary tablespaces and create the user so that the user's creation label dominates the creation label of the tablespaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12427 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of object must dominate schema |
| Long Text: | An attempt was made to create an object in a schema while at a label that does not dominate the schema's creation label. Your DBMS label must dominate the schema's creation label in order to create an object in the schema. |
| Repair Text: | From Oracle doc: Check the creation label of the schema and create the object while at a label that dominates the creation label of the schema. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12428 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient MAC privileges |
| Long Text: | An attempt was made to write to an object when you did not have sufficient privileges. You may have sufficient privileges to read the object, but do not have MAC write access to the object. |
| Repair Text: | From Oracle doc: Either retry the operation at the label of the object or ask the database administrator for sufficient MAC privileges to write the object. See the your documentation for Oracle security-related products for more information on MAC privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12429 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of comment must equal table or view |
| Long Text: | An attempt was made to comment a table or view while at a label that does not match the table's or view's creation label. Your DBMS label must match the table's or view's creation label in order to comment the table or view. |
| Repair Text: | From Oracle doc: Check the creation label of the table or view and add the comment while at a label that matches the creation label of the table or view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of trigger must equal table |
| Long Text: | An attempt was made to create or you issued a statement that tried to create a trigger on a table while at a label that does not match the table's creation label. Your DBMS label must match the table's creation label in order to create the trigger on the table. While the table may be visible due to enabled MAC privileges, MAC privileges cannot be used to create a trigger. |
| Repair Text: | From Oracle doc: Check the creation label of the table and create the trigger while at a label that matches the creation label of the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of user must dominate default profile |
| Long Text: | An attempt was made to assign a user a default profile when the user's creation label did not dominate the default profile's creation label. In order to assign a default profile to a user, the user's creation label must dominate the default profile's creation label. Your DBMS label must dominate both the user's and the default profile's creation labels in order to assign the user the default profile. |
| Repair Text: | From Oracle doc: Check the creation label of the default profile and create the user so that the user's creation label dominates the creation label of the default profile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of grant must equal label of procedure |
| Long Text: | An attempt was made to assign MAC privileges to a procedure at a label other than the creation label of the procedure. |
| Repair Text: | From Oracle doc: Grant MAC privileges to the procedure at the procedure's creation label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of default role %s must dominate user |
| Long Text: | An attempt was made to assign a default role to a user when the default role's creation label did not dominate the user's creation label. The default role's creation label must dominate the user's creation label. Your DBMS label also must dominate both the role's and user's creation label in order to assign a user a role. |
| Repair Text: | From Oracle doc: Check the creation labels of the user and role and assign only those roles whose creation labels dominate the creation label of the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12434 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of child record must dominate parent |
| Long Text: | An attempt was made to insert a child record with a label that does not dominate the corresponding parent record's label or update a parent record such that the child records would not dominate the corresponding parent's label. The label of a child record must always dominate that of its parent record. |
| Repair Text: | From Oracle doc: Check the label of the parent record and insert the child record while at a label that dominates the label of the parent record or update the label of the child record before updating the parent record so that the child can still dominate the parent after the update. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12435 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label of package body must equal package |
| Long Text: | An attempt was made to create a package body while at a label that does not match the corresponding package's creation label. Your DBMS label must match the package's creation label in order to create a package body. |
| Repair Text: | From Oracle doc: Check the creation label of the package and create the package body while at a label that matches the creation label of the package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | package body must exist to grant MAC privileges |
| Long Text: | An attempt was made to grant MAC privileges to a package when the package body does not exist. |
| Repair Text: | From Oracle doc: Create the package body for the package and then re-attempt the grant. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot write down to a database at a lower label |
| Long Text: | An attempt was made to perform a write operation in a secondary database. You can only perform write operations in your primary database. |
| Repair Text: | From Oracle doc: Connect directly to the secondary database to perform the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to validate constraint on all rows |
| Long Text: | You must have access to all rows in a table in order to attempt to enable a constraint. |
| Repair Text: | From Oracle doc: Either enable MAC privileges so that you can read all rows in the table, or downgrade all rows in the table so you can read them. Then enable the constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12439 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify ROWLABEL column |
| Long Text: | An attempt was made to modify the definition of the ROWLABEL column with the ALTER command. For example, you may have tried to lengthen the ROWLABEL column. |
| Repair Text: | From Oracle doc: Although the value of the ROWLABEL column can be changed, the ROWLABEL column definition cannot be modified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database has not been mounted in read-compatible mode |
| Long Text: | The requested secondary database was not started in read-compatible mode. In order for a database to be mounted by a higher level read-secure instance, the database must be mounted by its primary instance in read-compatible mode. |
| Repair Text: | From Oracle doc: Set the DB_MOUNT_MODE parameter to READ_COMPATIBLE in the secondary database and start the secondary database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | grant already exists at a different label |
| Long Text: | An attempt was made to grant a privilege that was previously granted at a different label. |
| Repair Text: | From Oracle doc: Check USER_SYS_GRANTS or USER_OBJ_GRANTS to identify the label of the privilege's previous grant. If you want to execute the grant at the new label, revoke the old grant and regrant the privilege while at the new label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12442 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must be at same label as user to modify default roles |
| Long Text: | An attempt was made to modify a user's default roles while at a label that does not match the user's creation label. Your DBMS label must match the user's creation label in order to alter a user. |
| Repair Text: | From Oracle doc: Check the ALL_USERS view to determine the creation label of the user and modify the user's default roles while at a label that matches the creation label of the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | audit option already exists at a different label |
| Long Text: | An attempt was made to audit an event that was previously audited at a different label. |
| Repair Text: | From Oracle doc: Check the DBA_STMT_AUDIT_OPTS or DBA_PRIV_AUDIT_OPTS dictionary views to identify the label of the previous audit statement. If you want to audit the event at the new label, stop the old audit (using the NOAUDIT statement) and re-audit the event while at the new label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file label is lower than instance label |
| Long Text: | An attempt was made to reuse a file with a label different than the database instance label. |
| Repair Text: | From Oracle doc: Examine the message stack for the file name. Remove the file or relabel it to match the database instance label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file label is higher than instance label |
| Long Text: | An attempt was made to reuse a file with a label different than the database instance label. You can only reuse files labeled at or below the instance label. |
| Repair Text: | From Oracle doc: Examine the message stack for the file name. Remove the file or relabel it to match the database instance label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12447 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-secure protocol used; connection denied |
| Long Text: | An attempt was made to connect to Trusted Oracle7 with a networking protocol that was not secure. You must use a secure networking protocol to connect via a remote location. |
| Repair Text: | From Oracle doc: Either connect to the database with a secure networking protocol or log in directly to the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12448 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | greatest lower bound resulted in an invalid operating system label |
| Long Text: | An attempt was made to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system. |
| Repair Text: | From Oracle doc: Examine the message stack for a more specific messages. See your installation or user's guide for information on invalid label generation. See the your documentation for Oracle security-related products for information on greatest lower bound (GLB) functions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | least upper bound resulted in an invalid operating system label |
| Long Text: | An attempt was made to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system. |
| Repair Text: | From Oracle doc: Examine the message stack for a more specific messages. See your installation or user's guide for information on invalid label generation. See the your documentation for Oracle security-related products for information on least upper bound (LUB) functions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12450 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal buffer overflow during label translation |
| Long Text: | An internal buffer used to translate labels overflowed. A possible cause could be a format mask you specified is too large. |
| Repair Text: | From Oracle doc: Try using a smaller format mask. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | format mask for TO_LABEL or TO_CHAR function is invalid |
| Long Text: | The format mask that you specified did not contain valid format codes for label conversion. |
| Repair Text: | From Oracle doc: Check the your documentation for Oracle security-related products for valid format codes. Correct the format mask and reattempt the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error initializing label context |
| Long Text: | An internal error occurred that prevented initialization of the label context. This may be caused by internal memory corruption or a software defect. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | binary label could not be translated into a %s |
| Long Text: | The binary label that you specified for conversion is not valid. |
| Repair Text: | From Oracle doc: Check the source of the binary label. Execute the conversion with a valid binary label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12454 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input %s does not contain expected punctuation or literal |
| Long Text: | The punctuation you supplied in the label string is inconsistent with the format you specified. |
| Repair Text: | From Oracle doc: Change the punctuation in the label string or format, whichever is appropriate, and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12455 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid internal format code found |
| Long Text: | In performing the requested translation, a format code was invalid. This message may result from memory corruption. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12456 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate format code specified in %s to label conversion |
| Long Text: | You may not specify duplicate string input when converting to a binary label. For example, 'SEN SENLEV' is an invalid format mask. |
| Repair Text: | From Oracle doc: Change the format mask and input string to specify a format code only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12457 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid length for MLSLABEL bind variable |
| Long Text: | A bind variable of type MLSLABEL is too long. |
| Repair Text: | From Oracle doc: Consult your documentation for proper datatype lengths. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12458 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the input %s could not be translated into a binary label |
| Long Text: | The input string you specified is not a valid binary label on your operating system. |
| Repair Text: | From Oracle doc: Check the input string, change any components so that they form a valid label, and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12459 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of columns in a Trusted Oracle table is 253 |
| Long Text: | A CREATE or ALTER TABLE statement tried to add more than 253 columns (not counting ROWLABEL) to a table. |
| Repair Text: | From Oracle doc: Specify no more than 253 columns in your CREATE or ALTER TABLE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12460 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the value %s for the MLS_LABEL_FORMAT parameter is not valid |
| Long Text: | The value for the MLS_LABEL_FORMAT parameter you specified does not contain a valid format mask. You must have a valid MLS_LABEL_FORMAT parameter for the database to start. |
| Repair Text: | From Oracle doc: Change this parameter setting in your INIT.ORA file to a correct value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12461 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid binary label |
| Long Text: | You provided a binary label in an OCI program's bind statement that was not a valid operating system label. |
| Repair Text: | From Oracle doc: Replace the invalid binary label with one that is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12470 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | process label could not be found |
| Long Text: | An error was encountered in translating the your operating system process label into a label number. |
| Repair Text: | From Oracle doc: Examine the message stack for a more specific message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12475 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot log in below DBLOW (%s) |
| Long Text: | An attempt was made to log in at a label dominated by DBLOW. You can only log in to Trusted Oracle between DBLOW and DBHIGH, inclusive. |
| Repair Text: | From Oracle doc: Either log in at a higher label, or lower DBLOW. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12476 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot log in above DBHIGH (%s) |
| Long Text: | An attempt was made to log in at a label dominating DBHIGH. You can only log in to Trusted Oracle between DBLOW and DBHIGH, inclusive. |
| Repair Text: | From Oracle doc: Either log in at a lower label, or raise DBHIGH. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12477 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot insert label below DBLOW (%s) |
| Long Text: | An attempt was made to explicitly insert a value below DBLOW into the ROWLABEL column, or tried to specify a value lower than DBLOW in a column of datatype MLSLABEL. Any label you insert into Trusted Oracle table must fall between DBLOW and DBHIGH, inclusive. |
| Repair Text: | From Oracle doc: Either lower the value of DBLOW, or specify a higher label on the INSERT or UPDATE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12478 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot insert label above DBHIGH (%s) |
| Long Text: | An attempt was made to explicitly insert a value above DBHIGH into the ROWLABEL column, or tried to specify a value higher than DBHIGH in a column of datatype MLSLABEL. Any label you insert into a Trusted Oracle table must fall between DBLOW and DBHIGH, inclusive. |
| Repair Text: | From Oracle doc: Either raise the value of DBHIGH, or specify a lower label on the INSERT or UPDATE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12480 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | secondary database changing between OS MAC and DBMS MAC modes |
| Long Text: | An attempt was made to access a secondary database while the secondary database was in the process of changing between OS MAC and DBMS MAC modes. |
| Repair Text: | From Oracle doc: Re-attempt the operation after the change is complete. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12485 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot find file label for %s |
| Long Text: | An error was encountered while reading the label of the specified file. |
| Repair Text: | From Oracle doc: Examine the message stack for an operating system message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12487 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to set label to DBHIGH or DBLOW |
| Long Text: | You must connect to Trusted Oracle using the INTERNAL keyword in order to set your label to DBHIGH or DBLOW. |
| Repair Text: | From Oracle doc: Connect to Trusted Oracle using INTERNAL, then set your label to DBHIGH or DBLOW. If you do not have privileges to connect using INTERNAL, contact your database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12488 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session label must be equal to %s |
| Long Text: | An attempt was made to log in to an OS MAC database at other than the database label. |
| Repair Text: | From Oracle doc: Log in from an OS process at the specified label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12489 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient MAC privileges to alter your session label |
| Long Text: | An attempt was made to alter your session label without the appropriate MAC privileges. You must have the appropriate MAC privileges in order to dynamically change your session label. Note that MAC privileges are not available in an OS MAC database, only in a DBMS MAC database. |
| Repair Text: | From Oracle doc: To change your session label, do one of the following: Change your operating system label. This is your only alternative in OS MAC mode. This can be done by logging out of the DBMS, changing your operating system label within the operating system, and then logging back into the DBMS. Note that, if you are logging into an OS MAC database, your operating system label must match the label of your primary database. Obtain the appropriate MAC privileges that allow you to dynamically change your session label within the DBMS. You need the READUP and WRITEUP MAC privileges to raise your session label, and the WRITEDOWN MAC privilege to lower your label, and all three to alter your label laterally. Note that changing your session label does not effect your operating system label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12490 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot alter DBMS label below username creation label (%s) |
| Long Text: | An attempt was made to alter your DBMS label to a label lower than that at which your username was created. You can only alter your DBMS label between your username's creation label and DBHIGH, within the limits of your clearance. |
| Repair Text: | From Oracle doc: Either do not alter your DBMS label below the specified label, or contact the database administrator to re-create your username at lower level. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12491 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change MAC mode when mounted in READ_COMPATIBLE mode |
| Long Text: | An attempt was made to change between OS and DB MAC mode while the database was mounted in READ_COMPATIBLE mode. |
| Repair Text: | From Oracle doc: Set the DB_MOUNT_MODE parameter to NORMAL and restart the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12494 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot mount secondary database labeled above DBLOW |
| Long Text: | The secondary database that you attempted to mount is labeled above DBLOW in the primary database. You can only mount a secondary database if that DBHIGH in that database (or, in OS MAC mode, the label of the database) is lower than DBLOW in your primary database. |
| Repair Text: | From Oracle doc: Determine if you really want to establish a read-secure link between the two databases. If so, relabel the secondary database so that DBHIGH in the secondary database is lower than DBLOW in the primary database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12495 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | multi-threaded server cannot be used with Trusted Oracle |
| Long Text: | The MTS_DISPATCHERS parameter is set in the initialization file, which initiated the configuration of the multi-threaded server. |
| Repair Text: | From Oracle doc: Remove the MTS_DISPATCHERS parameter from the initialization file and restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:listener failed to start a dedicated server process |
| Long Text: | The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly. |
| Repair Text: | From Oracle doc: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:listener received no CONNECT_DATA from client |
| Long Text: | No CONNECT_DATA was passed to the listener. |
| Repair Text: | From Oracle doc: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:listener was not given the SID in CONNECT_DATA |
| Long Text: | The SID was missing from the CONNECT_DATA. |
| Repair Text: | From Oracle doc: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in the CONNECT_DATA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS: listener could not resolve SID given in connect descriptor |
| Long Text: | The SID in the CONNECT_DATA was not found in the listener's tables. This error will be returned if the database instance has not registered with the listener; the instance may need to be started. |
| Repair Text: | From Oracle doc: Check to make sure that the SID specified is correct. The SIDs that are currently registered with the listener can be obtained by typing "LSNRCTL SERVICES <listener name>". These SIDs correspond to SID_NAMEs in TNSNAMES.ORA, or DB_NAMES in the initialization file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:listener failed to redirect client to service handler |
| Long Text: | The dispatcher terminated unexpectedly |
| Repair Text: | From Oracle doc: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:database lacks resources to handle the request for this SID |
| Long Text: | The dispatchers are busy handling other requests. |
| Repair Text: | From Oracle doc: Contact the DBA to increase the number of dispatchers servicing this SID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:service handler found but it is not accepting connections |
| Long Text: | The dispatchers are busy handling other requests and they notified the listener that they are temporarily busy. |
| Repair Text: | From Oracle doc: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:service handler found but it has not registered a redirect address |
| Long Text: | The dispatcher just came up and has not had time yet to register the address that a client should be redirected to. |
| Repair Text: | From Oracle doc: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:service handler found but it has registered for a different protocol |
| Long Text: | The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client. |
| Repair Text: | From Oracle doc: Contact the DBA to register a dispatcher on your protocol. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:listener does not currently know of service requested in connect descriptor |
| Long Text: | The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. |
| Repair Text: | - Wait a moment and try to connect a second time.;- Check which services are currently known by the listener by executing: lsnrctl services <listener name>;- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.;- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.;- Check for an event in the listener.log file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12528 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:listener: all appropriate instances are blocking new connections |
| Long Text: | All instances supporting the service requested by the client reported that they were blocking the new connections. This condition may be temporary, such as at instance startup. |
| Repair Text: | From Oracle doc: Attempt the connection again. If error persists, then contact the administrator to check the status of the instances. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12531 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:cannot allocate memory |
| Long Text: | Sufficient memory could not be allocated to perform the desired activity. |
| Repair Text: | From Oracle doc: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12532 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:invalid argument |
| Long Text: | An internal function received an invalid parameter. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12533 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:illegal ADDRESS parameters |
| Long Text: | An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport. |
| Repair Text: | From Oracle doc: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operation not supported |
| Long Text: | An internal function received a request to perform an operation that is not supported (on this machine). |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12535 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operation timed out |
| Long Text: | The requested connection could not be completed within the timeout period specified by the CONNECT_TIMEOUT parameter in listener.ora. This error arises from the tnslsnr. |
| Repair Text: | From Oracle doc: Either reconfigure CONNECT_TIMEOUT to be 0, which means wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher value. Or, if the timeout is unacceptably long, turn on tracing for further information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12536 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operation would block |
| Long Text: | An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking. |
| Repair Text: | From Oracle doc: None needed; this is an information message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12537 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | TNS:connection closed |
| Long Text: | "End of file" condition has been reached; partner has disconnected. |
| Repair Text: | From Oracle doc: None needed; this is an information message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12538 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no such protocol adapter |
| Long Text: | The protocol adapter requested (by way of the "(PROTOCOL=..)" keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adaptor is not installed. |
| Repair Text: | From Oracle doc: Install the protocol adapter or correct typographical error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12539 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:buffer over- or under-flow |
| Long Text: | Buffer too small for incoming data or too large for outgoing data. |
| Repair Text: | From Oracle doc: This restriction (which is associated with CONNECT DATA) is not normally visible to the user. For further details, turn on tracing and reexecute the operation; contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12540 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:internal limit restriction exceeded |
| Long Text: | Too many TNS connections open simultaneously. |
| Repair Text: | From Oracle doc: Wait for connections to close and re-try. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12541 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no listener |
| Long Text: | The connection request could not be completed because the listener is not running. |
| Repair Text: | From Oracle doc: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12542 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:address already in use |
| Long Text: | Specified listener address is already being used. |
| Repair Text: | From Oracle doc: Start your listener with a unique address. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12543 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:destination host unreachable |
| Long Text: | Contact can not be made with remote party. |
| Repair Text: | From Oracle doc: Make sure the network driver is functioning and the network is up. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12544 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:contexts have different wait/test functions |
| Long Text: | Two protocol adapters have conflicting wait/test functions. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12545 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Connect failed because target host or object does not exist |
| Long Text: | The address specified is not valid, or the program being connected to does not exist. |
| Repair Text: | From Oracle doc: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12546 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:permission denied |
| Long Text: | User has insufficient privileges to perform the requested operation. |
| Repair Text: | From Oracle doc: Acquire necessary privileges and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12547 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:lost contact |
| Long Text: | Partner has unexpectedly gone away, usually during process start-up. |
| Repair Text: | From Oracle doc: Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12548 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:incomplete read or write |
| Long Text: | A data send or receive failed. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12549 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operating system resource quota exceeded |
| Long Text: | The current user has exceeded the allotted resource assigned in the operating system. |
| Repair Text: | From Oracle doc: Acquire more operating system resource, or perform a different function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12550 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:syntax error |
| Long Text: | The supplied connect descriptor contains illegal syntax. |
| Repair Text: | From Oracle doc: Check the syntax of the connect descriptor in TNSNAMES.ORA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:missing keyword |
| Long Text: | The supplied connect descriptor is missing one or more TNS keywords. |
| Repair Text: | From Oracle doc: Check the syntax, and ensure all required keywords are present. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operation was interrupted |
| Long Text: | An internal operation was interrupted and could not complete. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12554 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | TNS:current operation is still in progress |
| Long Text: | An internal operation is still in progress. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12555 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:permission denied |
| Long Text: | User has insufficient privileges to perform the requested operation. |
| Repair Text: | From Oracle doc: Acquire necessary privileges and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12556 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no caller |
| Long Text: | TNS detected an incoming connect request but there was no caller. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12557 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:protocol adapter not loadable |
| Long Text: | On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned. |
| Repair Text: | From Oracle doc: For further details, turn on tracin and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12558 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:protocol adapter not loaded |
| Long Text: | On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned. |
| Repair Text: | From Oracle doc: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12560 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:protocol adapter error |
| Long Text: | A generic protocol adapter error occurred. |
| Repair Text: | From Oracle doc: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors.For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12561 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:unknown error |
| Long Text: | A generic protocol error occurred. |
| Repair Text: | From Oracle doc: For further details, turn on tracing and reexecute the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12562 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:bad global handle |
| Long Text: | Internal error - bad 'gbh' argument passed to TNS from caller. System may have been linked with old libraries. |
| Repair Text: | From Oracle doc: Not normally visible to the user, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12564 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:connection refused |
| Long Text: | The connect request was denied by the remote user (or TNS software). |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12566 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:protocol error |
| Long Text: | An unexpected TNS protocol error has occurred. |
| Repair Text: | From Oracle doc: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12569 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:packet checksum failure |
| Long Text: | The data received is not the same as the data sent. |
| Repair Text: | From Oracle doc: Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12570 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:packet reader failure |
| Long Text: | An error occurred during a data receive. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12571 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:packet writer failure |
| Long Text: | An error occurred during a data send. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12574 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:redirection denied |
| Long Text: | The connect request failed because it would have required redirection and the caller has requested no redirections. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12582 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:invalid operation |
| Long Text: | An internal function received an invalid request. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12583 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no reader |
| Long Text: | A send operation has been requested but partner has already disconnected. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12585 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:data truncation |
| Long Text: | A receive operation has completed with insufficient data to satisfy the user's request. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12589 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:connection not bequeathable |
| Long Text: | An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12590 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no I/O buffer |
| Long Text: | An attempt to perform an I/O operation failed because no buffer was available. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12591 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:event signal failure |
| Long Text: | The TNS software is unable to signal an event occurrence. |
| Repair Text: | From Oracle doc: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12592 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:bad packet |
| Long Text: | An ill-formed packet has been detected by the TNS software. |
| Repair Text: | From Oracle doc: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12593 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no registered connection |
| Long Text: | An attempt to solicit network event activity has failed because no connections are registered for event notification. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12595 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no confirmation |
| Long Text: | TNS is unable to get requested confirmation acknowledgment from remote partner. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12596 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:internal inconsistency |
| Long Text: | TNS has detected an internal inconsistency. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12597 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:connect descriptor already in use |
| Long Text: | Internal error - illegal use of connect descriptor. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12598 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:banner registration failed |
| Long Text: | The registration of a product banner with the Oracle server failed. |
| Repair Text: | From Oracle doc: This is an error which is not normally visible externally. Enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12599 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:cryptographic checksum mismatch |
| Long Text: | The data received is not the same as the data sent. |
| Repair Text: | From Oracle doc: Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS: %s open failed |
| Long Text: | The creation of a string in ORACLE NLS format failed. |
| Repair Text: | From Oracle doc: This is an internal error, enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:information flags check failed |
| Long Text: | The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished. |
| Repair Text: | From Oracle doc: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12611 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operation is not portable |
| Long Text: | Attempted operton is not portable. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12612 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:connection is busy |
| Long Text: | Attempted operation failed because it conflicts with an ongoing action or status of the connection. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12615 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:preempt error |
| Long Text: | A request to service an event failed because no event notification has yet been posted. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12616 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no event signals |
| Long Text: | The TNS software is unable to enable event signals. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12617 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:bad `what' type |
| Long Text: | The operation failed because the type of data specified is unknown. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12618 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:versions are incompatible |
| Long Text: | The two machines are running incompatible versions of TNS. |
| Repair Text: | From Oracle doc: Check the version numbers, and upgrade the machine with the smaller one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12619 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:unable to grant requested service |
| Long Text: | The connect request failed because requested service could not be provided by the local TNS software. |
| Repair Text: | From Oracle doc: If appropriate, reexecute with reduced service requirements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12620 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:requested characteristic not available |
| Long Text: | The connect request failed because a requested transport characteristic could not be supported by the remote TNS software. |
| Repair Text: | From Oracle doc: If appropriate, reexecute with reduced requirements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12622 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:event notifications are not homogeneous |
| Long Text: | An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12623 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:operation is illegal in this state |
| Long Text: | Connection is half-duplex and a full-duplex operation was attempted. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12624 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | TNS:connection is already registered |
| Long Text: | An attempt to register a connection for event notification failed because the connection is already registered. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12625 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:missing argument |
| Long Text: | An operation failed because an argument was missing" |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12626 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:bad event type |
| Long Text: | An attempt to register a connection for event notification failed because the event type is unknown. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12628 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no event callbacks |
| Long Text: | An attempt to register a connection for event notification failed because asynchronous callbacks are not available. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12629 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TNS:no event test |
| Long Text: | An attempt to register a connection for event notification failed because the ability to test for events is not available. |
| Repair Text: | From Oracle doc: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12630 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Native service operation not supported |
| Long Text: | An operation requested by a user is not supported by the native services component. |
| Repair Text: | From Oracle doc: This may be an internal error if the operation should have been supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12631 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Username retrieval failed |
| Long Text: | The authentication service failed to retrieve the name of a user. |
| Repair Text: | From Oracle doc: Enable tracing to determine which routine is failing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12632 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Role fetch failed |
| Long Text: | The authentication service failed to retrieve one of the user's roles. |
| Repair Text: | From Oracle doc: Enable tracing to determine which routine is failing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12633 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No shared authentication services |
| Long Text: | The list of authentication services specified by the user does not match those supported by the process. |
| Repair Text: | From Oracle doc: Either specify another list or relink the executable with the desired services. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12634 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Memory allocation failed |
| Long Text: | Process was unable to allocate memory. |
| Repair Text: | From Oracle doc: Terminate other processes in order to reclaim needed memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12635 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No authentication adapters available |
| Long Text: | The executable was not linked with any authentication service adapters but the SQLNET.ORA parameter that determines whether or not authentication is required was set to true. |
| Repair Text: | From Oracle doc: Either disable the parameter or relink the executable with service adapters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12636 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Packet send failed |
| Long Text: | A process was unable to send a packet to another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred. |
| Repair Text: | From Oracle doc: If the cause is not obvious, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12637 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Packet receive failed |
| Long Text: | A process was unable to receive a packet from another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred. |
| Repair Text: | From Oracle doc: If the cause is not obvious, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12638 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Credential retrieval failed |
| Long Text: | The authentication service failed to retrieve the credentials of a user. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12639 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication service negotiation failed |
| Long Text: | No match was found between the types of authentication services that the client supports and those that the server is using. |
| Repair Text: | From Oracle doc: Possible solutions: 1. Change the entry in SQLNET.ORA that determines which services are to be used. 2. Relink the client with at least one of the authentication service adapters that the server supports. 3. Relink the server with at least one of the authentication service adapters that the client supports. 4. Disable authentication on both the client and server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12640 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication adapter initialization failed |
| Long Text: | The function specified in the authentication table entry for the service failed. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12641 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication service failed to initialize |
| Long Text: | The authentication service failed during initialization. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12642 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No session key |
| Long Text: | A process has no session key associated with it because the authentication service being used does not use one. |
| Repair Text: | From Oracle doc: If a session key is required, use another authentication service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12643 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Client received internal error from server |
| Long Text: | The client process received an error from the server that indicated that an internal SQL*Net native services error had occurred. |
| Repair Text: | From Oracle doc: Enable tracing on both processes and attempt to recreate the problem. If successful in recreating the problem, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12644 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication service initialization failed |
| Long Text: | The routine called to initialize the authentication adapter failed. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. A likely cause is that memory is exhausted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12645 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Parameter does not exist. |
| Long Text: | A SQLNET.ORA parameter from which a value was needed does not exist. |
| Repair Text: | From Oracle doc: Set the parameter in the parameter file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12646 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid value specified for boolean parameter |
| Long Text: | The value specified for a parameter was set to a value other than true/false or on/off. |
| Repair Text: | From Oracle doc: Correct the value of the parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12647 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Authentication required |
| Long Text: | The parameter that controls whether authentication is required was set to true, but the executable does not have an authentication service linked in. |
| Repair Text: | From Oracle doc: Either re-link the executable with an authentication service adapter or disable the parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12648 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Encryption or data integrity algorithm list empty |
| Long Text: | A SQL*Net list-of-algorithms parameter was empty, e.g. "()". |
| Repair Text: | From Oracle doc: Change the list to contain the name of at least one installed algorithm, or remove the list entirely if every installed algorithm is acceptable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12649 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unknown encryption or data integrity algorithm |
| Long Text: | A SQL*Net list-of-algorithms parameter included an algorithm name that was not recognized. |
| Repair Text: | From Oracle doc: Either remove that algorithm name, correct it if it was misspelled, or install the driver for the missing algorithm. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12650 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No common encryption or data integrity algorithm |
| Long Text: | The client and server have no algorithm in common for either encryption or data integrity or both. |
| Repair Text: | From Oracle doc: Choose sets of algorithms that overlap. In other words, add one of the client's algorithm choices to the server's list or vice versa. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12651 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Encryption or data integrity algorithm unacceptable |
| Long Text: | The algorithm the server chose to use for encryption or data integrity was not one of the choices acceptable to the client. This is either the result of an internal error, of a network data transmission error, or of deliberate tampering with the transmitted data. |
| Repair Text: | From Oracle doc: For further details, turn on tracing, re-execute the operation, and contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12652 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | String truncated |
| Long Text: | Not enough memory was allocated for a string so it had to be truncated |
| Repair Text: | From Oracle doc: If it is OK that the string is truncated, then it is not an error. Otherwise, call the routine that reported the error again with a larger string buffer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12653 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication control function failed |
| Long Text: | The control function utilized by the authentication service driver failed. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12654 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication conversion failed |
| Long Text: | The authentication service was unable to convert the credentials of a user from the format specific to the format into the ORACLE format. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12655 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Password check failed |
| Long Text: | The authentication service being used was unable to verify the provided password. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12656 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cryptographic checksum mismatch |
| Long Text: | The cryptographic checksum received with a packet of incoming data didn't match the checksum computed by the receiving end. This indicates that the packet was tampered with or otherwise corrupted in transit. |
| Repair Text: | From Oracle doc: Look for sources of data corruption, perhaps including deliberate tampering. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12657 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No algorithms installed |
| Long Text: | The near side of the connection required the use of a service (either encryption or checksumming) when no algorithms for that service were installed. |
| Repair Text: | From Oracle doc: Remove the "ON" requirement for that service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12658 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Native service required but TNS version is incompatible |
| Long Text: | A process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that a native service (authentication, encryption, etc.) be used. |
| Repair Text: | From Oracle doc: Relink the calling executable and retry the connection or eliminate the requirement that the service be used on the server side. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12659 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error received from other process |
| Long Text: | An error was received by one or more services from the process on the other side of the connection. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error(s). The error(s) is (are) not returned directly because an error generated by a server may not make sense on the client side and vice-versa. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12660 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Encryption or crypto-checksumming parameters incompatible |
| Long Text: | One side of the connection specified "REQUIRED" for encryption or crypto-checksumming, while the other side specified "REJECTED". |
| Repair Text: | From Oracle doc: Change the "REQUIRED" side to "REQUESTED" if the you want encryption or crypto-checksumming to be optional, or change the "REJECTED" side to "ACCEPTED" if you do not want the service to be optional. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12661 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Protocol authentication to be used |
| Long Text: | The SQL*Net authentication service has determined that the SQL*Net transport protocol in use is to be utilized to authenticate a user's identity. |
| Repair Text: | From Oracle doc: This error is used solely to communicate information between the authentication service and the SQL*Net session layer and should not be visible to the user. If the error is seen, contact Worldwide customer support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12662 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | proxy ticket retrieval failed |
| Long Text: | The authentication adapter used by SQL*Net failed to retrieve the credentials needed to authenticate a database link. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12663 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Services required by client not available on the server |
| Long Text: | Service(s) that was (were) required by the client process were not available on the server process. |
| Repair Text: | From Oracle doc: Configure the server with the services required by the client (best solution) or delete the requirement from the configuration file of the client (least secure). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12664 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Services required by server not available on the client |
| Long Text: | Service(s) that was (were) required by the server process were not available on the client process. |
| Repair Text: | From Oracle doc: Configure the client with the services required by the server (best solution) or delete the requirement from the configuration file of the server (least secure). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12665 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NLS %s open failed |
| Long Text: | A native service was unable to make a string available for use by the National Language Support component. |
| Repair Text: | From Oracle doc: Make sure the National Language Support component has been properly. If it has, enable tracing and report the problem to Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12666 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Dedicated server: outbound transport protocol different from inbound |
| Long Text: | The protocol specified for an externally-identified outbound connection from a dedicated server (database link) was not the same as that used for the inbound connection. It is not possible for SQL*Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the dedicated server. |
| Repair Text: | From Oracle doc: Specify the same protocol in the SQL*Net connect string or alias for the outbound connection as that used for the inbound connection |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12667 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Shared server: outbound transport protocol different from inbound |
| Long Text: | The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same as that used for the inbound connection. It is not possible for SQL*Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the shared server. |
| Repair Text: | From Oracle doc: Specify the same protocol in the SQL*Net connect string or alias for the outbound connection as that used for the inbound connection |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12668 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Dedicated server: outbound protocol does not support proxies |
| Long Text: | The protocol specified to perform an externally-identified proxy connection (database link) from a dedicated server does not support proxy connections. |
| Repair Text: | From Oracle doc: Specify a protocol in the SQL*Net connect string or alias used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12669 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Shared server: outbound protocol does not support proxies |
| Long Text: | The protocol specified to perform an externally-identified proxy connection (database link) from a shared server does not support proxy connections. |
| Repair Text: | From Oracle doc: Specify a protocol in the SQL*Net connect string or alias used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12670 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Incorrect role password |
| Long Text: | A password supplied for a role could not be validated by the authentication service. |
| Repair Text: | From Oracle doc: Supply the correct password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12671 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Shared server: adapter failed to save context |
| Long Text: | The adapter for the authentication service failed when it tried to save the data needed for proxy connections (database links) through the multi-threaded server. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. Contact Worldwide Customer Support if the reason is not obvious. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12672 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Database logon failure |
| Long Text: | The authentication service adapter in use encountered an error it attempted to validate the logon attempt of a user. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error encountered by the adapter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12673 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Dedicated server: context not saved |
| Long Text: | A connection was marked as being a proxy connection (database link) from a dedicated server but no inbound context was present. |
| Repair Text: | From Oracle doc: This error should not normally be visible to the user. Contact Oracle Customer Support |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12674 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Shared server: proxy context not saved |
| Long Text: | A connection was marked as being a proxy connection (database link) from a shared server but no inbound context was present. |
| Repair Text: | From Oracle doc: This error should not normally be visible to the user. Contact Oracle Customer Support |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12675 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | External user name not available yet |
| Long Text: | The authentication service in use was not able to return the external name of a user of the ORACLE server because it is not available to the service yet. |
| Repair Text: | From Oracle doc: This is just an information message and should not normally be visible to the user. If the error does appear, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12676 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server received internal error from client |
| Long Text: | The server process received an error from the client which indicated that an internal SQL*Net native services error had occurred. |
| Repair Text: | From Oracle doc: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12677 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication service not supported by database link |
| Long Text: | The authentication service used by the proxy process (database link) was unable to find the adapter being used by the client in its list of authentication mechanisms. |
| Repair Text: | From Oracle doc: Specify an authentication adapter that is shared by the client and the server being used for the database link. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12678 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Authentication disabled but required |
| Long Text: | The configuration parameters that control whether SQL*Net authentication is disabled or required were both set to TRUE. |
| Repair Text: | From Oracle doc: Set one or both of the parameters to FALSE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12679 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Native services disabled by other process but required |
| Long Text: | The remote process has disabled native services but the local process requires them. |
| Repair Text: | From Oracle doc: Enable native services on the remote process or disable them locally. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12680 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Native services disabled but required |
| Long Text: | The process has disabled native services but at least one service is required. |
| Repair Text: | From Oracle doc: Enable native services or change the configuration file so that none of the available services are required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12681 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Login failed: the SecurID card does not have a pincode yet |
| Long Text: | The SecurID card that is used to logon to Oracle, does not have a pincode assigned to it. |
| Repair Text: | From Oracle doc: Use one of the programs supplied by Security Dynamics to assign a pincode to the card. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12682 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Login failed: the SecurID card is in next PRN mode |
| Long Text: | The SecurID card and the SecurID server are out of sync and the server requires the next cardcode to re-synchronize the card. |
| Repair Text: | From Oracle doc: Use one of the programs supplied by Security Dynamics to re-synchronize the SecurID card. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12683 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | encryption/crypto-checksumming: no Diffie-Hellman seed |
| Long Text: | The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA parameters file for SQL*Net. |
| Repair Text: | From Oracle doc: Add this line to SQLNET.ORA: sqlnet.crypto_seed = "randomly-chosen text" |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12684 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | encryption/crypto-checksumming: Diffie-Hellman seed too small |
| Long Text: | The "sqlnet.crypto_seed" parameter in the SQLNET.ORA parameter file for SQL*Net is too small. |
| Repair Text: | From Oracle doc: Add more randomly-chosen text to it, perhaps using Network Manager. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12685 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Native service required remotely but disabled locally |
| Long Text: | A native service is required by the remote process but native services have been disabled locally. |
| Repair Text: | From Oracle doc: Enable native services locally or change the configuration parameters on the remote host so that no native services are required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12686 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid command specified for a service |
| Long Text: | An operation which does not exist was specified for a native service. |
| Repair Text: | From Oracle doc: This is a programming error and should not normally be visible to the user. If the error does appear, contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12687 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Database link failed: credentials expired |
| Long Text: | The credentials that are used to authenticate the user for the requested database link have expired. |
| Repair Text: | From Oracle doc: Renew your credentials. Refer to the documentation specific for your Network Authentication Adapter on how to do this. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12688 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Login failed: the SecurID server rejected the new pincode |
| Long Text: | There are a number of reasons why the SecurID server would refuse a pincode: - The user might not have permission to make up his own pincode. - The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters. - The pincode contains any non alpha-numeric characters. |
| Repair Text: | From Oracle doc: Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12689 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server Authentication required, but not supported |
| Long Text: | Server Authentication is required for this connection, but not supported by both sides of the connection. |
| Repair Text: | From Oracle doc: Make sure both sides of the connection have the correct version of Secure Network Services, and that the Authentication Adapter supports Server Authentication. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12690 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server Authentication failed, login cancelled |
| Long Text: | Server Authentication is required, but the server's credentials were found invalid by the client. |
| Repair Text: | From Oracle doc: Make sure that the server has a valid set of credentials. Refer to your authentication adapter specific documentation on how to do this. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12699 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Native service internal error |
| Long Text: | An internal error occurred in the native services component. |
| Repair Text: | From Oracle doc: Enable tracing to determine the exact error. Contact Worldwide Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12700 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid NLS parameter value (%s) |
| Long Text: | An invalid NLS initialization parameter was specified. |
| Repair Text: | From Oracle doc: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CREATE DATABASE character set is not known |
| Long Text: | The character set specified in the CREATE DATABASE command does not exist on the system. |
| Repair Text: | From Oracle doc: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12702 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid NLS parameter %s used in SQL function |
| Long Text: | An invalid parameter or value was entered in the NLS parameter string in a SQL function. |
| Repair Text: | From Oracle doc: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this character set conversion is not supported |
| Long Text: | An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets. |
| Repair Text: | From Oracle doc: Use character sets available on the system in the CONVERT function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | character set mismatch |
| Long Text: | One of the following: The string operands (other than an NLSPARAMS argument) to an operator or built-in function do not have the same character set. An NLSPARAMS operand is not in the database character set. String data with character set other than the database character set is passed to a built-in function not expecting it. The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS. A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted. A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column. An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter. |
| Repair Text: | From Oracle doc: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12705 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid or unknown NLS parameter value specified |
| Long Text: | There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set. |
| Repair Text: | From Oracle doc: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION command, see Oracle8i SQL Reference. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this CREATE DATABASE character set is not allowed |
| Long Text: | An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted. |
| Repair Text: | From Oracle doc: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12707 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while getting create database NLS parameter %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while loading create database NLS parameter %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while loading create database character set |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12710 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CREATE CONTROLFILE character set is not known |
| Long Text: | The character set specified when creating the control file is unknown. |
| Repair Text: | From Oracle doc: Specify a known character set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12711 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this CREATE CONTROLFILE character set is not allowed |
| Long Text: | It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa. |
| Repair Text: | From Oracle doc: Create the correct control file for machine and character set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12712 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new character set must be a superset of old character set |
| Long Text: | When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC. |
| Repair Text: | From Oracle doc: Specify a superset character set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system appears too busy for parallel query execution |
| Long Text: | Load on the system is too high to perform parallel queries. |
| Repair Text: | From Oracle doc: Re-execute serially or wait until the system load is reduced. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error signaled in parallel query server %s |
| Long Text: | A parallel query server reached an exception condition. |
| Repair Text: | From Oracle doc: Check the following error message for the cause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel query server lost contact with coordinator |
| Long Text: | A parallel query server lost contact with the foreground (coordinator) process/thread. |
| Repair Text: | From Oracle doc: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel query server lost contact with another server |
| Long Text: | A parallel query server lost contact with another server. |
| Repair Text: | From Oracle doc: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel query server appears to have died |
| Long Text: | Cannot find process information for a parallel query server thread. |
| Repair Text: | From Oracle doc: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12805 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel query server died unexpectedly |
| Long Text: | A parallel query server died unexpectedly, PMON cleaning up the process. |
| Repair Text: | From Oracle doc: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Customer Support. See trace file for more details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12806 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not get background process to hold enqueue |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: This error should not normally occur. If it persists, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12807 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | process queue could not receive parallel query message |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: This error should not normally occur. If it persists, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12808 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot set %s_INSTANCES greater than number of instances %s |
| Long Text: | An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command to a value larger than the number of available instances. |
| Repair Text: | From Oracle doc: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12809 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot set %s_INSTANCES when mounted in exclusive mode |
| Long Text: | An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode. |
| Repair Text: | From Oracle doc: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle parallel server mounted in SHARED or PARALLEL mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PARALLEL_MAX_SERVERS must be less than or equal to %s |
| Long Text: | An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system. |
| Repair Text: | From Oracle doc: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, %s |
| Long Text: | An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS. |
| Repair Text: | From Oracle doc: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one PARALLEL or NOPARALLEL clause may be specified |
| Long Text: | PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command. |
| Repair Text: | From Oracle doc: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value for PARALLEL or DEGREE must be greater than 0 |
| Long Text: | PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement. |
| Repair Text: | From Oracle doc: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12814 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one CACHE or NOCACHE clause may be specified |
| Long Text: | CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement. |
| Repair Text: | From Oracle doc: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12815 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value for INSTANCES must be greater than 0 |
| Long Text: | PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT. |
| Repair Text: | From Oracle doc: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel create index fastpath operation |
| Long Text: | The parallel create index fastpath operation event has been set. |
| Repair Text: | From Oracle doc: Set this event only under the supervision Oracle development. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12817 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel query option must be enabled |
| Long Text: | A parallel query option feature has been invoked but this option has not been enabled. |
| Repair Text: | From Oracle doc: Enable the parallel query option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12818 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option in PARALLEL clause |
| Long Text: | An unrecognized option was used within a PARALLEL clause. |
| Repair Text: | From Oracle doc: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12819 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing options in PARALLEL clause |
| Long Text: | PARALLEL clause cannot be empty. |
| Repair Text: | From Oracle doc: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12820 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for DEGREE |
| Long Text: | Invalid value for DEGREE was specified within a PARALLEL clause. |
| Repair Text: | From Oracle doc: Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12821 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for INSTANCES |
| Long Text: | An invalid value for INSTANCES was specified within a PARALLEL clause. |
| Repair Text: | From Oracle doc: Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12822 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate option in PARALLEL clause |
| Long Text: | DEGREE or INSTANCES was specified more than once within a PARALLEL clause. |
| Repair Text: | From Oracle doc: Specify each desired PARALLEL clause option only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12823 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | default degree of parallelism may not be specified here |
| Long Text: | The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command. |
| Repair Text: | From Oracle doc: Respecify with an explicit degree of parallelism. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12824 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | INSTANCES DEFAULT may not be specified here |
| Long Text: | INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command. |
| Repair Text: | From Oracle doc: Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12825 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | explicit degree of parallelism must be specified here |
| Long Text: | The DEGREE option was omitted from an ALTER DATABASE RECOVER command. |
| Repair Text: | From Oracle doc: Respecify with an explicit degree of parallelism. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12826 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hung parallel query server was killed |
| Long Text: | The parallel query server was hung and subsequently killed. |
| Repair Text: | From Oracle doc: Re-execute the query and report suspicious events in the trace file to Oracle Customer Support if the error persists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12827 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient parallel query slaves available |
| Long Text: | PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired. |
| Repair Text: | From Oracle doc: Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12828 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Can't start parallel transaction - distributed transaction in progress |
| Long Text: | PDML transaction cannot be started because a distributed transaction is in progress. |
| Repair Text: | From Oracle doc: Change the DML statement to exclude updates to remote tables and re-execute the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12829 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Deadlock - itls occupied by siblings at block %s of file %s |
| Long Text: | A parallel statement failed because all ITLS in the current block are occupied by siblings of the same transaction. |
| Repair Text: | From Oracle doc: Increase the value of MAXTRANS of the block or reduce the degree of parallelism for the statement. Re-execute the statement. Report suspicious events in the trace file to Oracle Customer Support if the error persists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12830 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE |
| Long Text: | After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued. |
| Repair Text: | From Oracle doc: Execute COMMIT or ROLLBACK before issuing another SQL command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12831 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Must COMMIT or ROLLBACK after executing INSERT with APPEND hint |
| Long Text: | After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued. |
| Repair Text: | From Oracle doc: Execute COMMIT or ROLLBACK before issuing another SQL command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12832 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Could not allocate slaves on all specified instances |
| Long Text: | After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query. |
| Repair Text: | From Oracle doc: To allow results to be returned by successfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12833 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Coordinator's instance not a member of parallel_instance_group |
| Long Text: | The coordinator's instance must be a member of the PARALLEL_INSTANCE_GROUP in which this operation will be run. |
| Repair Text: | From Oracle doc: Either add the coordinator's instance to the current PARALLEL_INSTANCE_GROUP or change PARALLEL_INSTANCE_GROUP. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12834 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Instance group name, '%s', too long, must be less than %s characters |
| Long Text: | The instance group name is too long. |
| Repair Text: | From Oracle doc: Either shorten the name or get rid of the instance group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12835 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No instances are active in the OPS_ADMIN_GROUP |
| Long Text: | There must be at least one instance in the OPS_ADMIN_GROUP in order to execute a query on global views. |
| Repair Text: | From Oracle doc: Change the value of OPS_ADMIN_GROUP. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12838 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot read/modify an object after modifying it in parallel |
| Long Text: | Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted. |
| Repair Text: | From Oracle doc: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12839 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify an object in parallel after modifying it |
| Long Text: | Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted. |
| Repair Text: | From Oracle doc: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12840 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot access remote table in a parallel transaction |
| Long Text: | Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued. |
| Repair Text: | From Oracle doc: Commit/roll back the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12841 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot alter the session parallel DML state within a transaction |
| Long Text: | Transaction in progress. |
| Repair Text: | From Oracle doc: Commit or roll back the transaction and then re-execute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12842 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | schema modified during parallel execution |
| Long Text: | Schema modified during the parse phase of parallel processing. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12843 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pdml lock not held properly on the table |
| Long Text: | The coodinator crashed or released the lock on the partition which the slave is trying to aquire. |
| Repair Text: | From Oracle doc: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the PDML again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12980 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | checkpoint option not allowed with SET UNUSED |
| Long Text: | An attempt was made to specify checkpoint option with SET UNUSED. |
| Repair Text: | From Oracle doc: Remove the checkpoint option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12981 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop column from an object type table |
| Long Text: | An attempt was made to drop a column from an object type table. |
| Repair Text: | From Oracle doc: This action is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12982 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop column from a nested table |
| Long Text: | An attempt was made to drop a column from a nested table. |
| Repair Text: | From Oracle doc: This action is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12983 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop all columns in a table |
| Long Text: | An attempt was made to drop all columns in a table. |
| Repair Text: | From Oracle doc: Make sure at least one column remains in the table after the drop column operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12984 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop partitioning column |
| Long Text: | An attempt was made to drop a column used as the partitioning key. |
| Repair Text: | From Oracle doc: This action is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12985 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is read only, cannot drop column |
| Long Text: | An attempt was made to drop column from a partition/subpartition on a read-only tablespace. |
| Repair Text: | From Oracle doc: Set the tablespace to read write and resubmit statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12986 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE |
| Long Text: | An attempt was made to access a table with columns in partially dropped state (that is, drop column operation was interrupted). |
| Repair Text: | From Oracle doc: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12987 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot combine drop column with other operations |
| Long Text: | An attempt was made to combine drop column with other ALTER TABLE operations. |
| Repair Text: | From Oracle doc: Ensure that drop column is the sole operation specified in ALTER TABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12988 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop column from table owned by SYS |
| Long Text: | An attempt was made to drop a column from a system table. |
| Repair Text: | From Oracle doc: This action is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12989 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for checkpoint interval |
| Long Text: | An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1). |
| Repair Text: | From Oracle doc: Correct checkpoint interval and resubmit statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12990 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate option specified |
| Long Text: | Duplicate option specified in statement. |
| Repair Text: | From Oracle doc: Remove the duplicate option and resubmit statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12991 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column is referenced in a multi-column constraint |
| Long Text: | An attempt was made to drop a column referenced by some constraints. |
| Repair Text: | From Oracle doc: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12992 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop parent key column |
| Long Text: | An attempt was made to drop a parent key column. |
| Repair Text: | From Oracle doc: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12993 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is offline, cannot drop column |
| Long Text: | An attempt was made to drop a column from a partition/subpartition on an offline tablespace. |
| Repair Text: | From Oracle doc: Bring the tablespace online and resubmit statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12994 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | drop column option only allowed once in statement |
| Long Text: | An attempt was made to repeat the drop column option in a single statement. |
| Repair Text: | From Oracle doc: Separate drop column options into different statements and resubmit statements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12995 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no columns in partially dropped state |
| Long Text: | An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns. |
| Repair Text: | From Oracle doc: Cannot submit this statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12996 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop system-generated virtual column |
| Long Text: | An attempt was made to drop a virtual column generated by the system. |
| Repair Text: | From Oracle doc: This action is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-12997 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop primary key column from an index-organized table |
| Long Text: | An attempt was made to drop a primary key column from an index- organized table. |
| Repair Text: | From Oracle doc: This action is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dimension number is out of range |
| Long Text: | The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE. |
| Repair Text: | From Oracle doc: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dimensions mismatch error |
| Long Text: | The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match. |
| Repair Text: | From Oracle doc: Make sure that the number of dimensions in the HHCODEs match. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified level is out of range |
| Long Text: | The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE. |
| Repair Text: | From Oracle doc: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified range for a dimension is invalid |
| Long Text: | The specified range for a dimension is invalid. |
| Repair Text: | From Oracle doc: Make sure that the lower bound (LB) is less than the upper bound (UB). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified buffer size is invalid |
| Long Text: | The buffer size for a function is not valid. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recursive HHCODE function error |
| Long Text: | An error occurred in a recursively called HHCODE function. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified cell number is invalid |
| Long Text: | The cell identifier is either less than 0 or greater that (2^ndim - 1). |
| Repair Text: | From Oracle doc: Make sure that the cell identifier is between 0 and (2^ndim - 1). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an invalid HEX character was detected |
| Long Text: | A character that is not in the range [0-9] or [A-Fa-f] was detected. |
| Repair Text: | From Oracle doc: Verify that all characters in a string are in [0-9] or [A-Fa-f]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified date format has an invalid component |
| Long Text: | Part of specified date format is invalid. |
| Repair Text: | From Oracle doc: Verify that the date format is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified date %s is invalid |
| Long Text: | The specified date string has a bad component or does not match the specified format string. |
| Repair Text: | From Oracle doc: Make sure that the components of the date string are valid and that the date and format strings match. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an invalid number of arguments has been specified |
| Long Text: | An invalid number of arguments was specified for an SDO function. |
| Repair Text: | From Oracle doc: Verify the syntax of the function call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value is out of range |
| Long Text: | A specified dimension value is outside the range defined for that dimension. |
| Repair Text: | From Oracle doc: Make sure that all values to be encoded are within the defined dimension range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an invalid window type was specifed |
| Long Text: | An invalid window type was specified. |
| Repair Text: | From Oracle doc: Valid window types are RANGE, PROXIMITY, POLYGON. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified topology was not INTERIOR or BOUNDARY |
| Long Text: | A topology was specified that was not INTERIOR or BOUNDARY. |
| Repair Text: | From Oracle doc: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a topology identifier outside the range of 1 to 8 was specified |
| Long Text: | A topology identifier outside the range of 1 to 8 was specified. |
| Repair Text: | From Oracle doc: Specify a topology in the range of 1 to 8. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the window definition is not valid |
| Long Text: | The number of values used to define the window does not correspond to the window type. |
| Repair Text: | From Oracle doc: Verify that the number of values used to defined the window is correct for the window type and number of dimensions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad partition definition |
| Long Text: | The partition common code was not correctly decoded. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. This is an internal error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unrecognized line partition shape |
| Long Text: | The shape of a 2-D line partition could not be determined. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad distance type |
| Long Text: | The specified distance type is invalid. |
| Repair Text: | From Oracle doc: The only supported distance functions are EUCLID and MANHATTAN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | coordinates out of bounds |
| Long Text: | Vertex coordinates lie outside the valid range for specified dimension. |
| Repair Text: | From Oracle doc: Re-define vertex coordinates within specified boundaries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | coordinate is NULL |
| Long Text: | A vertex coordinate has a NULL value. |
| Repair Text: | From Oracle doc: Re-define vertex coordinate to have non-NULL value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | element not continuous |
| Long Text: | The coordinates defining a geometric element are not connected. |
| Repair Text: | From Oracle doc: Re-define coordinates for the geometric element. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | polygon crosses itself |
| Long Text: | The coordinates defining a polygonal geometric element represent crossing segments. |
| Repair Text: | From Oracle doc: Re-define coordinates for the polygon. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | interior element interacts with exterior element |
| Long Text: | An interior element of a geometric object interacts with the exterior element of that object. |
| Repair Text: | From Oracle doc: Re-define coordinates for the geometric elements. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | polygon has less than three segments |
| Long Text: | The coordinates defining a polygonal geometric element represent less than three segments. |
| Repair Text: | From Oracle doc: Re-define the coordinates for the polygon. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | polygon does not close |
| Long Text: | The coordinates defining a polygonal geometric element represent an open polygon. |
| Repair Text: | From Oracle doc: Re-define the coordinates of the polygon. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown element type for element %s.%s.%s |
| Long Text: | The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value. |
| Repair Text: | From Oracle doc: Re-define the geometric element type in the layer_SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See Oracle Spatial User's Guide and Reference for an explanation of SDO_ETYPE and its possible values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to read dimension definition from %s |
| Long Text: | There was a problem reading the dimension definition from the layer_SDODIM table. |
| Repair Text: | From Oracle doc: Verify that the layer_SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to update spatial index for element %s.%s.%s |
| Long Text: | Another error will accompany this message that will indicate the problem. |
| Repair Text: | From Oracle doc: Correct any accompanying errors. If no accompanying error message appears then contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to subdivide tile |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Note any accompanying errors and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to compare tile with element %s.%s.%s |
| Long Text: | The spatial relationship between a generated tile and the specified element could not be determined. This is an internal error. |
| Repair Text: | From Oracle doc: Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors then note any errors which accompany ORA-13041 and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SDO_LEVEL and SDO_NUMTILES combination |
| Long Text: | An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the layer_SDOLAYER table. The most likely cause is that the columns are NULL. |
| Repair Text: | From Oracle doc: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial User's Guide and Reference. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to read meta data from the layer_SDOLAYER table |
| Long Text: | An error was encountered reading the layer meta data from the layer_SDOLAYER table. |
| Repair Text: | From Oracle doc: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified tile size exceeds the maximum resolution |
| Long Text: | The tile size specified for fixed size tessellation exceeds the maximum resolution as computed from the layer meta data. |
| Repair Text: | From Oracle doc: See the Oracle Spatial User's Guide and Reference for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a lesser tile size value than the current one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid compatibility flag |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13046 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number of arguments |
| Long Text: | An invalid number of arguments were specified for an SDO_GEOM function. |
| Repair Text: | From Oracle doc: Refer to the Oracle Spatial Cartridge user documentation for a description of the syntax and semantics of the relevant SDO_GEOM function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13047 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to determine ordinate count from table layer_SDOLAYER |
| Long Text: | An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer. |
| Repair Text: | From Oracle doc: Verify that the layer_SDOLAYER table has a valid value for the column SDO_ORDCNT. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13048 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recursive SQL fetch error |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13049 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to determine tolerance value from table layer_SDODIM |
| Long Text: | An SDO_GEOM function was unable to determine the tolerance value for the SDO layer layer. |
| Repair Text: | From Oracle doc: Verify that the layer_SDODIM table has a valid value for the column SDO_TOLERANCE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13050 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to construct spatial object |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13051 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to initialize spatial object |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported geometric type for geometry %s.%s |
| Long Text: | The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by the Oracle Spatial Cartridge. |
| Repair Text: | From Oracle doc: Check Oracle Spatial User's Guide and Reference for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of geometric elements in argument list exceeded |
| Long Text: | The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded. |
| Repair Text: | From Oracle doc: Check Oracle Spatial User's Guide and Reference for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it in as an argument in a call to the SDO_GEOM function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recursive SQL parse error |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13055 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle object %s does not exist in specified table |
| Long Text: | The requested object is not present in the specified table. |
| Repair Text: | From Oracle doc: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spatial table %s not found |
| Long Text: | The specified spatial table does not exist. |
| Repair Text: | From Oracle doc: Check the Spatial Data option data dictionary to make sure that the table is registered. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spatial table %s exists |
| Long Text: | The specified spatial table is registered in the Spatial Data data dictionary. |
| Repair Text: | From Oracle doc: Remove the existing table from the Spatial Data option data dictionary or use a different name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spatial table %s is not partitioned |
| Long Text: | The specified spatial table is not partitioned. |
| Repair Text: | From Oracle doc: Check the Spatial Data option data dictionary and make sure that a high water mark is set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spatial table %s has no partition key defined |
| Long Text: | The specified spatial table does not have a partition key defined. |
| Repair Text: | From Oracle doc: Check the Spatial Data option data dictionary and make sure that the table is partitioned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid count mode %s |
| Long Text: | The specified count mode is not valid. |
| Repair Text: | From Oracle doc: Alter the count mode. Valid count modes are ESTIMATE or EXACT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle table %s does not exist |
| Long Text: | The specified Oracle table does not exist. |
| Repair Text: | From Oracle doc: Check the Oracle data dictionary and make sure that the table exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace %s not found |
| Long Text: | The specified tablespace does not exist. |
| Repair Text: | From Oracle doc: Check the Oracle data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace %s is already allocated |
| Long Text: | The specified tablespace is already allocated to the spatial table. |
| Repair Text: | From Oracle doc: Allocate another tablespace name to the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace %s is not allocated to table %s |
| Long Text: | The specified tablespace is not allocated to the specified spatial table. |
| Repair Text: | From Oracle doc: Allocate the tablespace to the spatial table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13117 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition %s not found |
| Long Text: | The specified partition does not exist. |
| Repair Text: | From Oracle doc: Verify the name of the partition by checking the Spatial Data option data dictionary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13119 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | source and target tablespaces are identical |
| Long Text: | Identical source and target tablespaces were specified when trying to move partition. |
| Repair Text: | From Oracle doc: Specify different source and target tablespaces if you wish to move a partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to create child partition |
| Long Text: | The creation of a child partition failed. |
| Repair Text: | From Oracle doc: Check for other errors that accompany this error and correct them first. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | child partition %s not found |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column %s is already defined |
| Long Text: | The specified column is already defined for the spatial table. |
| Repair Text: | From Oracle doc: Use a different column name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to determine column id for column %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition key is already set |
| Long Text: | A partition key is already set for the spatial table. |
| Repair Text: | From Oracle doc: Only one partition key can be specified per spatial table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to determine class for spatial table %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate target partition |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | current tiling level exceeds user specified tiling level |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13129 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | HHCODE column %s not found |
| Long Text: | The specified spatial column does not exist. |
| Repair Text: | From Oracle doc: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13135 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to alter spatial table |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13136 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null common code generated |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13137 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate tablespace sequence number |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13138 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not determine name of object %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13139 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not obtain column definition for %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13140 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid target type |
| Long Text: | The specified target type is not valid. |
| Repair Text: | From Oracle doc: Substitute a valid target type. Valid target types are TABLE or VIEW. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13141 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid RANGE window definition |
| Long Text: | The RANGE window specified is not correctly defined. |
| Repair Text: | From Oracle doc: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (for example, lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13142 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid PROXIMITY window definition |
| Long Text: | The PROXIMITY window specified is not correctly defined. |
| Repair Text: | From Oracle doc: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13143 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid POLYGON window definition |
| Long Text: | The POLYGON window specified is not correctly defined. |
| Repair Text: | From Oracle doc: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13144 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | target table %s not found |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13145 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate range list |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13146 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not find table substitution variable %s |
| Long Text: | The partition name substitution variable string was not found in the SQL filter. |
| Repair Text: | From Oracle doc: The substitution variable string must be in the SQL filter to indicate where that partition name should be placed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13147 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate MBR |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13148 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate SQL filter |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13149 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate next sequence number for spatial table %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Document messages and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to insert exception record |
| Long Text: | Operation failed to insert a record into the exception table. |
| Repair Text: | From Oracle doc: Fix any other errors reported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to remove exception record |
| Long Text: | Operation failed to insert a record into the exception table. |
| Repair Text: | From Oracle doc: Fix any other errors reported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid HHCODE type |
| Long Text: | Specified HHCODE type is not valid. |
| Repair Text: | From Oracle doc: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid high water mark specified |
| Long Text: | The highwater mark must be greater than or equal to zero. |
| Repair Text: | From Oracle doc: Make sure that the highwater mark is an integer greater than or equal to zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13154 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid precision specified |
| Long Text: | The precision specified is out of range. |
| Repair Text: | From Oracle doc: The precision must be an integer greater than or equal to zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number of dimensions specified |
| Long Text: | The number of dimensions specified is out of range. |
| Repair Text: | From Oracle doc: The number of dimension must be between 1 and 32. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13156 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table to be registered %s.%s is not empty |
| Long Text: | The specified table has rows in it. |
| Repair Text: | From Oracle doc: Make sure that the table to be registered is empty. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13157 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle error ORA%s encountered while %s |
| Long Text: | Specified Oracle error was encountered. |
| Repair Text: | From Oracle doc: Correct the Oracle error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13158 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle object %s does not exist |
| Long Text: | The specified object does not exist. |
| Repair Text: | From Oracle doc: Verify that the specified object exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13159 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle table %s already exists |
| Long Text: | The specified table already exists. |
| Repair Text: | From Oracle doc: Drop the specified table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13181 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to determine length of column %s_SDOINDEX.SDO_CODE |
| Long Text: | The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined. |
| Repair Text: | From Oracle doc: Make sure that the layer_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13182 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to read element %s.%s.%s |
| Long Text: | The specified element could not be read from the layer_SDOGEOM table. |
| Repair Text: | From Oracle doc: Verify that the specified element exists in the table. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13183 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported geometric type for geometry %s.%s |
| Long Text: | The geometry type in the layer_SDOGEOM table is unsupported. |
| Repair Text: | From Oracle doc: Modify the geometry type to be one of the supported types. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13184 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to initialize tessellation package |
| Long Text: | Initialization of the tessellation package failed. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13185 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate initial HHCODE |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13186 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fixed tile size tessellation failed |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13187 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subdivision failed |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13188 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cell decode failed |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13189 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recursive SQL parse failed |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13190 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recursive SQL fetch failed |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13191 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to read SDO_ORDCNT value |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13192 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to read number of element rows |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13193 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to allocate space for geometry |
| Long Text: | There was insufficient memory to read the geometry from the database. |
| Repair Text: | From Oracle doc: Validate the geometry. Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13194 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to decode supercell |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13195 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate maximum tile value |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Record the error messages that are returned and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13196 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to compute supercell for element %s.%s.%s |
| Long Text: | The system was unable to compute the minimum bounding HHCODE or supercell for the geometry. |
| Repair Text: | From Oracle doc: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13197 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | element %s.%s.%s is out of range |
| Long Text: | Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the layer_SDODIM table. |
| Repair Text: | From Oracle doc: Verify that the geometry is valid and within the defined domain. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13198 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Spatial Cartridge error: %s |
| Long Text: | There was an internal error in some Spatial Cartridge stored procedure. |
| Repair Text: | From Oracle doc: Record the sequence of procedure calls or events that preceded this error and contact Oracle Customer Support if the error message text does not clearly specify the cause of the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13199 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error [%s] in spatial indexing. |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support with the exact error text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid parameters supplied in CREATE INDEX statement |
| Long Text: | An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement. |
| Repair Text: | From Oracle doc: Check Oracle Spatial User's Guide and Reference for the number, syntax, and semantics of expected parameters for spatial index creation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to create or insert into the SDO_INDEX_METADATA table |
| Long Text: | An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it. |
| Repair Text: | From Oracle doc: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to read SDO_GEOM_METADATA table |
| Long Text: | An error encountered while trying to read SDO_GEOM_METADATA table. |
| Repair Text: | From Oracle doc: Check that SDO_GEOM_METADATA table exists and there is an entry in the table for the current geometry table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to create spatial index table |
| Long Text: | An error was encountered while trying to create the spatial index table. |
| Repair Text: | From Oracle doc: Check that the user has create table privilege in the current schema and that the user has sufficient quota in the default or specified tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error while parsing spatial index parameters |
| Long Text: | An internal error was encountered while parsing the index parameters. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support with the exact error text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error [%s] while creating the spatial index |
| Long Text: | An internal error was encountered while creating the spatial index. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support with the exact error text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect use of the [%s] operator |
| Long Text: | An error was encountered while evaluating the specified operator. |
| Repair Text: | From Oracle doc: Check the parameters and the return type of the specified operator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error while evaluating [%s] operator |
| Long Text: | An internal error was encountered. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support with the exact error text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error while reading SDO_INDEX_METADATA table |
| Long Text: | An internal error was encountered while trying to read SDO_INDEX_METADATA table. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. Note this and accompanying error numbers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error inserting data into the index table |
| Long Text: | An error was encountered while trying to insert data into the spatial index table. Likely causes are: Insufficient quota in the current tablespace User does not appropriate privileges |
| Repair Text: | From Oracle doc: Check the accompanying error messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to tessellate the window object |
| Long Text: | An internal error was encountered while trying to tessellate the window object. |
| Repair Text: | From Oracle doc: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to compare tile with the window object |
| Long Text: | The spatial relationship between a generated tile and the specified window object could not be determined. |
| Repair Text: | From Oracle doc: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors then note any accompanying errors and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13213 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to generate spatial index for window object |
| Long Text: | Another error, indicating the real cause of the problem, should accompany this error. |
| Repair Text: | From Oracle doc: Correct any accompanying errors. If no accompanying error message appears then contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13214 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to compute supercell for window object |
| Long Text: | The system was unable to compute the minimum bounding tile or supercell for the geometry. |
| Repair Text: | From Oracle doc: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | window object is out of range |
| Long Text: | Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the SDO_GEOM_METADATA table. |
| Repair Text: | From Oracle doc: Verify that the geometry is valid and within the defined domain. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to update spatial index |
| Long Text: | Another error will accompany this message that will indicate the problem. |
| Repair Text: | From Oracle doc: Correct any accompanying errors. If no accompanying error message appears then contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid parameters supplied in ALTER INDEX statement |
| Long Text: | An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement. |
| Repair Text: | From Oracle doc: Check Oracle Spatial User's Guide and Reference for the number, syntax, and semantics of expected parameters for spatial alter index command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | max number of supported index tables reached for [%s] index |
| Long Text: | An ADD_INDEX parameter is passed to ALTER INDEX when the number of existing spatial index tables is already at maximum. |
| Repair Text: | From Oracle doc: Delete one of the spatial index tables before adding another spatial index table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to create spatial index table [%s] |
| Long Text: | An error was encountered while trying to create the spatial index table. |
| Repair Text: | From Oracle doc: There is a table in the index's schema with the specified name. The create index will try to create a spatial index table with this name. Either rename this table or change the name of the index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13220 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to compare tile with the geometry |
| Long Text: | The spatial relationship between a generated tile and the specified geometry could not be determined. |
| Repair Text: | From Oracle doc: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors then note any errors which accompany ORA-13220 and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13221 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown geometry type in the geometry object |
| Long Text: | The SDO_GTYPE attribute in the geometry object contains an invalid value |
| Repair Text: | From Oracle doc: Re-define the geometric type in the geometry table using one of the supported SDO_GTYPE values. See Oracle Spatial User's Guide and Reference for an explanation of SDO_GTYPE and its possible values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13222 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to compute supercell for geometry in %s |
| Long Text: | The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table. |
| Repair Text: | From Oracle doc: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13223 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate entry for %s in SDO_GEOM_METADATA table |
| Long Text: | There are duplicate entries for the given table and column value pair in the SDO_GEOM_METADATA table. |
| Repair Text: | From Oracle doc: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the SDO_GEOME_METADATA table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13224 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified index name is too long for a spatial index |
| Long Text: | An index name is specified which is longer than the supported length of the spatial index name. |
| Repair Text: | From Oracle doc: Check the supported size of the index name and reduce the size of the index name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13225 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified index table name is too long for a spatial index |
| Long Text: | A spatial index table name is specified which is longer than the supported length. |
| Repair Text: | From Oracle doc: Check the supported size of the spatial index table name and reduce the size of the index name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13226 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | interface not supported without a spatial index |
| Long Text: | The geometry table does not have a spatial index. |
| Repair Text: | From Oracle doc: Verify that the geometry table referenced in the spatial operator has a spatial index on it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13227 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SDO_LEVEL values for the two index tables do not match |
| Long Text: | The SDO_LEVEL values for the two spatial index tables used in the spatial join operator do not match. |
| Repair Text: | From Oracle doc: Verify that two compatible indexes are used for the spatial join operator. Indexes are compatabile if they have the same SDO_LEVEL and SDO_NUMTILES values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13249 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support with the exact error text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to modify metadata table entries |
| Long Text: | The user requesting the operation does not have the appropriate privileges on the referenced tables. |
| Repair Text: | From Oracle doc: Check that the specified feature and geometry table names are correct and then verify that the current user has at least SELECT privilege on those tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate entry %s in metadata table |
| Long Text: | The specified entry already exists in the metadata table. |
| Repair Text: | From Oracle doc: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | layer table %s does not exist |
| Long Text: | Data migration source table layer_SDOGEOM does not exist. |
| Repair Text: | From Oracle doc: Ensure that the specified layer name is correct and that the corresponding spatial layer tables exist in the current schema. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | geometry table %s does not exist |
| Long Text: | The specified geometry table does not exist in the current schema. |
| Repair Text: | From Oracle doc: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | geometry column %s does not exist in table %s |
| Long Text: | The specified table does not have a column of type SDO_GEOMETRY. |
| Repair Text: | From Oracle doc: Alter or re-create the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column %s in table %s is not of type SDO_GEOMETRY |
| Long Text: | The column intended for storing the geometry is not of type SDO_GEOMETRY. |
| Repair Text: | From Oracle doc: Alter the column definition to be of type SDO_GEOMETRY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13264 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | geometry identifier column %s does not exist in table %s |
| Long Text: | The specified table does not contain a GID column. |
| Repair Text: | From Oracle doc: Confirm that the GID column name was correctly specified and that it exists in the specified table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | geometry identifier column %s in table %s is not of type NUMBER |
| Long Text: | GID column is not of type NUMBER. |
| Repair Text: | From Oracle doc: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error inserting data into table %s |
| Long Text: | An OCI error occurred or the user has insufficient quota in the active tablespace or the rollback segments are too small. |
| Repair Text: | From Oracle doc: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13267 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error reading data from layer table %s |
| Long Text: | There was an error reading the geometry data from the layer_SDOGEOM table. |
| Repair Text: | From Oracle doc: Verify that layer_SDOGEOM and layer_SDODIM exist. If they do then run VALIDATE_GEOMETRY on the specified layer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13268 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error obtaining dimension information from SDO_GEOM_METADATA |
| Long Text: | There is no entry in SDO_GEOM_METADATA for the specified geometry table. |
| Repair Text: | From Oracle doc: Verify that the table SDO_GEOM_METADATA exists. If it does, insert an entry for the destination geometry table with the dimension information obtained from the source layer_SDODIM table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13269 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error [%s] encountered when processing geometry table |
| Long Text: | An internal error occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support with the exact error message text. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCI error %s |
| Long Text: | OCI error while processing the layer or geometry tables. |
| Repair Text: | From Oracle doc: Take the appropriate steps to correct the OCI specific error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error allocating memory for geometry object |
| Long Text: | There was insufficient memory for the geometry object. |
| Repair Text: | From Oracle doc: Make more memory available to the current session/process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13272 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | geometric object %s in table %s is invalid |
| Long Text: | The specified object failed the geometric integrity checks performed by VALIDATE_GEOMETRY. |
| Repair Text: | From Oracle doc: Consult Oracle Spatial User's Guide and Reference for information on the geometric integrity checks performed by VALIDATE_GEOMETRY and correct the geometry definition if required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13273 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dimension metadata table %s does not exist |
| Long Text: | The layer_SDODIM table does not exist. |
| Repair Text: | From Oracle doc: Verify that the specified layer name is correct and that the layer_SDODIM table exists in the current schema. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13330 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid MASK |
| Long Text: | The MASK you passed to RELATE function is not valid. |
| Repair Text: | From Oracle doc: Verify that the mask is not NULL. See Oracle Spatial User's Guide and Reference for a list of supported masks. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a point geometry has more than one coordinate |
| Long Text: | A geometry, specified as being a point, has more than one coordinate in its definition. |
| Repair Text: | From Oracle doc: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon then set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object then remove the extraneous coordinates from its definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a line geometry has less than two coordinates |
| Long Text: | A geometry, specified as being a line, has less than two coordinates in its definition. |
| Repair Text: | From Oracle doc: A line must consist of at least two distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an arc geometry has less than three coordinates |
| Long Text: | A geometry, specified as being an arc, has less than three coordinates in its definition. |
| Repair Text: | From Oracle doc: An arc must consist of at least three distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13343 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a polygon geometry has less than four coordinates |
| Long Text: | A geometry, specified as being a polygon, has less than four coordinates in its definition. |
| Repair Text: | From Oracle doc: A polygon must consist of at least four distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an arcpolygon geometry has less than five coordinates |
| Long Text: | A geometry, specified as being an arcpolygon, has less than six coordinates in its definition. |
| Repair Text: | From Oracle doc: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected, the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a compound polygon geometry has less than five coordinates |
| Long Text: | A geometry, specified as being a compound polygon, has less than five coordinates in its definition. |
| Repair Text: | From Oracle doc: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line each of which must be described using three and at least two distinct coordinates respectively. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13346 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the coordinates defining an arc are collinear |
| Long Text: | Invalid definition of an arc. An arc is defined using three non-collinear coordinates. |
| Repair Text: | From Oracle doc: Alter the definition or the arc or set the SDO_ETYPE or SDO_GTYPE to the line type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13347 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the coordinates defining an arc are not distinct |
| Long Text: | Two or more of the three points defining an arc are the same. |
| Repair Text: | From Oracle doc: Alter the definition of the arc ensuring that three distinct coordinate values are used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13348 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | polygon boundary is not closed |
| Long Text: | The boundary of a polygon does not close. |
| Repair Text: | From Oracle doc: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13349 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | polygon boundary crosses itself |
| Long Text: | The boundary of a polygon intersects itself. |
| Repair Text: | From Oracle doc: Correct the geometric definition of the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two or more rings of a complex polygon touch |
| Long Text: | The inner or outer rings of a complex polygon touch. |
| Repair Text: | From Oracle doc: All rings of a complex polygon must be disjoint. Correct the geometric description of the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | two or more rings of a complex polygon overlap |
| Long Text: | The inner or outer rings of a complex polygon overlap. |
| Repair Text: | From Oracle doc: All rings of a complex polygon must be disjoint. Correct the geometric description of the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the coordinates do not describe a circle |
| Long Text: | The set of coordinates used to describe a circle are incorrect. |
| Repair Text: | From Oracle doc: Confirm that the set of coordinates actually represent points on the circumference of a circle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ELEM_INFO_ARRAY not grouped in threes |
| Long Text: | The ELEM_INFO_ARRAY in SDO_GEOMETRY has more or fewer elements than expected. |
| Repair Text: | From Oracle doc: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect offset in ELEM_INFO_ARRAY |
| Long Text: | The offset field in ELEM_INFO_ARRAY of SDO_GEOMETRY references an invalid array subscript in SDO_ORDINATE_ARRAY. |
| Repair Text: | From Oracle doc: Confirm that the offset is a valid array subscript in SDO_ORINATE_ARRAY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13355 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SDO_ORDINATE_ARRAY not grouped by number of dimensions specified |
| Long Text: | The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user. |
| Repair Text: | From Oracle doc: Confirm that the number of dimensions is consistent with data representation in SDO_ORINATE_ARRAY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13356 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | adjacent points in a geometry are redundant |
| Long Text: | There are repeated points in the sequence of coordinates. |
| Repair Text: | From Oracle doc: Remove the redundant point. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13357 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | extent type does not contain 2 points |
| Long Text: | Extent type should be represented by 2 points: lower left and upper right. |
| Repair Text: | From Oracle doc: Confirm that there are only 2 points for extent type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13358 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | circle type does not contain 3 points |
| Long Text: | Circle type should be represented by 3 distinct points on the circumference. |
| Repair Text: | From Oracle doc: Confirm that there are only 3 points for circle type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13359 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | extent does not have an area |
| Long Text: | The 2 points representing the extent are identical. |
| Repair Text: | From Oracle doc: Confirm that the 2 points describing the extent type are distinct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid subtype in a compound type |
| Long Text: | This subtype is not allowed within the ETYPE specified. |
| Repair Text: | From Oracle doc: Refer to the Oracle Spatial User's Guide and Reference for type definitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not enough sub-elements within a compound ETYPE |
| Long Text: | The compound type declare more sub-elements than actually defined. |
| Repair Text: | From Oracle doc: Confirm that the number of sub-elements is consistent with the compound type declaration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | disjoint sub-element in a compound polygon |
| Long Text: | Compound polygon must describe an enclosed area. |
| Repair Text: | From Oracle doc: Confirm that all sub-elements are connected. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no valid ETYPE in the geometry |
| Long Text: | None of the ETYPEs within the geometry is supported. |
| Repair Text: | From Oracle doc: Confirm that there is at least one valid ETYPE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle GeoImage internal error, arguments: %s, %s, %s, %s, %s |
| Long Text: | This is an internal Oracle GeoImage error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported geoimage format |
| Long Text: | The GeoImage format is not supported. |
| Repair Text: | From Oracle doc: Confirm that the GeoImage format is valid and supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL destination |
| Long Text: | The object specified as the destination is NULL. |
| Repair Text: | From Oracle doc: Confirm that the object specified as the destination is not NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL source geometry |
| Long Text: | The source GeoImage has a NULL geometry. |
| Repair Text: | From Oracle doc: Verify that the geometry of the source GeoImage is not NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not a local source |
| Long Text: | An attempt has been made to modify a GeoImage which is not stored in the database. |
| Repair Text: | From Oracle doc: Import the GeoImage in order to modify it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13405 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL source |
| Long Text: | The object specified as the source is NULL. |
| Repair Text: | From Oracle doc: Confirm that the object specified as the source is not NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported image processing command %s |
| Long Text: | The image processing command specified is not supported for a GeoImage. |
| Repair Text: | From Oracle doc: Consult the Oracle interMedia manual to verify which image processing commands are supported within an Oracle GeoImage method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unrecognized space type qualifier %s |
| Long Text: | The GeoImage space type qualifier is invalid. |
| Repair Text: | From Oracle doc: Use a valid space type qualifier (RASTER or MODEL). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL table name |
| Long Text: | The table name parameter is NULL. |
| Repair Text: | From Oracle doc: Verify that the parameter used for the table name is not NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13409 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle table %s does not exist. |
| Long Text: | The table specified does not exist. |
| Repair Text: | From Oracle doc: Verify that the table name used is valid and the table exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13410 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL column name |
| Long Text: | The column name parameter is NULL. |
| Repair Text: | From Oracle doc: Verify that the parameter used for the column name is not NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13411 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle column %s does not exist. |
| Long Text: | The column specified does not exist. |
| Repair Text: | From Oracle doc: Verify that the column name used is valid and the column exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13412 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ROWID |
| Long Text: | The ROWID value used in not valid. |
| Repair Text: | From Oracle doc: Verify that the ROWID value used is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13413 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not select the GeoImage for initialization" |
| Long Text: | The GeoImage in the table could not be selected. |
| Repair Text: | From Oracle doc: Verify that the GeoIMage is present in the table and the supplied parameters are valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13414 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not update the table containing the GeoImage |
| Long Text: | The table containing the GeoImage could not be updated. |
| Repair Text: | From Oracle doc: Verify that the table exists and is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13415 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid domain |
| Long Text: | The SDO_DIMINFO value used is not valid or the SDO_GEOMETRY supplied is not defined in the domain. |
| Repair Text: | From Oracle doc: Verify that the SDO_DIMINFO value is valid, and that the SDO_GEOMETRY is defined within the domain specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13416 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid geometry, arguments %s |
| Long Text: | The SDO_GEOMETRY value used is not valid. |
| Repair Text: | From Oracle doc: Verify that the SDO_GEOMETRY is valid, consult the Oracle Spatial User's Guide and Reference for a list of valid geometries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13417 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | undefined raster to model space transformation |
| Long Text: | The raster to model space transformation associated with a GeoImage is undefined. |
| Repair Text: | From Oracle doc: Verify that the GeoImage format is valid and that the particular operation is supported for that format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13418 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | undefined model to raster space transformation |
| Long Text: | The model to raster space transformation associated with a GeoImage is undefined. |
| Repair Text: | From Oracle doc: Verify that the GeoImage format is valid and that the particular operation is supported for that format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13419 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid latitude value |
| Long Text: | A latitude value outside the valid range [-90,90] has been used. |
| Repair Text: | From Oracle doc: Verify that the GeoImage geometry definition is within the domain. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13420 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid model to raster space transformation |
| Long Text: | The model to raster space transformation associated with a GeoImage is not valid or cannot be calculated. |
| Repair Text: | From Oracle doc: Verify that the transformation is supported and that the GeoImage format is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13421 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid raster to model space transformation |
| Long Text: | The raster to model space transformation associated with a GeoImage is not valid or cannot be calculated. |
| Repair Text: | From Oracle doc: Verify that the transformation is supported and that the GeoImage format is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13422 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | uninitialized source |
| Long Text: | The LOB used for the source is not initialized. |
| Repair Text: | From Oracle doc: Verify that the source is properly initialized. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13423 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | empty source |
| Long Text: | The LOB used for the source is empty. |
| Repair Text: | From Oracle doc: Verify that the source is properly initialized and data has been imported into it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13424 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | uninitialized destination |
| Long Text: | The LOB used for the destination is not initialized. |
| Repair Text: | From Oracle doc: Verify that the destination is properly initialized. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13425 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | empty destination |
| Long Text: | The LOB used for the destination is empty. |
| Repair Text: | From Oracle doc: Verify that the destination is properly initialized and data has been imported into it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13426 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported raster origin |
| Long Text: | The raster origin specified is not supported. |
| Repair Text: | From Oracle doc: Verify that the origin specified is supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13427 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown raster origin |
| Long Text: | The value specified for the raster origin is invalid. |
| Repair Text: | From Oracle doc: Verify that the value used to specify the raster origin is valid and supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13428 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | source does not exist |
| Long Text: | The source does not exist or cannot be accessed. |
| Repair Text: | From Oracle doc: Verify that the source specification is correct and accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13429 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation %s not supported on GeoImage type %s |
| Long Text: | The specified operation is not supported on the particular GeoImage type. |
| Repair Text: | From Oracle doc: Verify that the operation is supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | model coordinate system not supported |
| Long Text: | The model specified for the definition of the coordinate system is not supported. |
| Repair Text: | From Oracle doc: Verify that the model value is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL crop geometry |
| Long Text: | The geometry used to crop a GeoImage is NULL. |
| Repair Text: | From Oracle doc: Verify that the geometry used for the crop operation is not NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13442 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid scaling parameters %s %s |
| Long Text: | The parameters used in the scale operation are invalid. |
| Repair Text: | From Oracle doc: Verify that the scaling parameters are greater than zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unrecognized scale mode %s |
| Long Text: | The scale mode used in the scale operation is invalid. |
| Repair Text: | From Oracle doc: Consult the Oracle8i interMedia Audio, Image, and Video User's Guide and Reference for a list of valid scale mode qualifiers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported conversion format %s |
| Long Text: | The format specified for conversion is invalid or unsupported. |
| Repair Text: | From Oracle doc: Verify that the conversion format specified is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13461 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid tag/key %s |
| Long Text: | The tag or key is invalid. |
| Repair Text: | From Oracle doc: Verify that the format version is supported or the format is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13462 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid tie point |
| Long Text: | One of the tie points is invalid. |
| Repair Text: | From Oracle doc: Verify that the tie points used are valid (for example all raster tie points are >= 0). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13463 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported GeoTIFF geometry definition |
| Long Text: | The combination of keys/tags used to define the geometry footprint of the GeoImage is not supported. |
| Repair Text: | From Oracle doc: Verify that the GeoTIFF format version is supported and the format is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13464 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported conversion |
| Long Text: | The format specified for conversioin is not supported. In GeoTIFF only a limited number of tags/keys combinations are supported for conversion. |
| Repair Text: | From Oracle doc: Verify that the GeoTIFF format version is supported and conversion to the desired format is available. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-13499 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | This is an internal Spatial Cartridge error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one LOCAL clause may be specified |
| Long Text: | CREATE INDEX statement contained more than one LOCAL clause. |
| Repair Text: | From Oracle doc: Specify LOCAL option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOCAL clause contradicts previosly specified GLOBAL clause |
| Long Text: | CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause. |
| Repair Text: | From Oracle doc: Specify LOCAL or GLOBAL clause, but not both. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one GLOBAL clause may be specified |
| Long Text: | CREATE INDEX statement contained more than one GLOBAL clause. |
| Repair Text: | From Oracle doc: Specify GLOBAL option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GLOBAL clause contradicts previosly specified LOCAL clause |
| Long Text: | CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause. |
| Repair Text: | From Oracle doc: Specify GLOBAL or LOCAL clause, but not both. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing PARTITION keyword |
| Long Text: | Keyword PARTITION missing. |
| Repair Text: | From Oracle doc: Supply missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing RANGE keyword |
| Long Text: | Keyword RANGE missing. |
| Repair Text: | From Oracle doc: Supply missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid partition name |
| Long Text: | A partition name of the form identifier is expected but not present. |
| Repair Text: | From Oracle doc: Enter an appropriate partition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing LESS keyword |
| Long Text: | Keyword LESS missing. |
| Repair Text: | From Oracle doc: Supply missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing THAN keyword |
| Long Text: | Keyword THAN missing. |
| Repair Text: | From Oracle doc: Supply missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound may not be specified for a LOCAL index partition |
| Long Text: | While parsing a CREATE INDEX statement to create a LOCAL partitioned index, partition_description of one of partitions was found to contain VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table. |
| Repair Text: | From Oracle doc: Remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this physical attribute may not be specified for an index partition |
| Long Text: | Unexpected option was encountered while parsing physical attributes of an index partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for hash partitions. |
| Repair Text: | From Oracle doc: Remove invalid option(s) from the list of physical attributes of an index partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | names assigned to resulting partitions must be distinct |
| Long Text: | Names of partitions resulting from splitting of an existing table or index partition are not distinct. |
| Repair Text: | From Oracle doc: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resulting partition name conflicts with that of an existing partition |
| Long Text: | Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index. |
| Repair Text: | From Oracle doc: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate partition name |
| Long Text: | Name of a partition of a table or index being created is not unique. |
| Repair Text: | From Oracle doc: Rename partition(s) to ensure that their names are unique among partitions of the table or index being created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of partitioning columns is 16 |
| Long Text: | Number of columns in a partitioning column list exceeded the legal limit of 16. |
| Repair Text: | From Oracle doc: Modify partitioning column list so that it consists of at most 16 columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many partition descriptions |
| Long Text: | CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 65535. |
| Repair Text: | From Oracle doc: Reduce the number of partitions to not exceed 65535. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | underlying table of a LOCAL partitioned index must be partitioned |
| Long Text: | An attempt was made to create a LOCAL partitioned index on a non-partitioned table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created on a non-partitioned table. |
| Repair Text: | From Oracle doc: Correct the statement and re-enter it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound list contains too many elements |
| Long Text: | Partition bound list contained more elements than there are partitioning columns. |
| Repair Text: | From Oracle doc: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound list contains too few elements |
| Long Text: | Partition bound list contained fewer elements than there are partitioning columns. |
| Repair Text: | From Oracle doc: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound element must be one of: %s, datetime or interval literal, number, or MAXVALUE |
| Long Text: | Partition bound list contained an element of invalid type (that is, not a number, non-empty string, datetime or interval literal, or MAXVALUE). |
| Repair Text: | From Oracle doc: Ensure that all elements of partition bound list are of valid type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this physical attribute may not be specified for a table partition |
| Long Text: | Unexpected option was encountered while parsing physical attributes of a table partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for hash partitions. |
| Repair Text: | From Oracle doc: Remove invalid option(s) from the list of physical attributes of a table partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAXVALUE must be specified for all columns |
| Long Text: | In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns. |
| Repair Text: | From Oracle doc: Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | creation of LOCAL partitioned cluster indices is not supported |
| Long Text: | An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal. |
| Repair Text: | From Oracle doc: Remove LOCAL along with partition_descriptions, if any, from the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | creation of GLOBAL partitioned cluster indices is not supported |
| Long Text: | An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal. |
| Repair Text: | From Oracle doc: Remove PARTITION BY RANGE clause along with partition_descriptions from the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of partitions of LOCAL index must equal that of the underlying table |
| Long Text: | An attempt was made to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table. |
| Repair Text: | From Oracle doc: Correct the CREATE INDEX statement to specify a correct number of partitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PARTITION may not be specified for a snapshot or a snapshot log |
| Long Text: | PARTITION option was encountered while parsing a definition of a snapshot or a snapshot log. |
| Repair Text: | From Oracle doc: Ensure that a definition of a SNAPSHOT does not include invalid options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PARTITION and CLUSTER clauses are mutually exclusive |
| Long Text: | Definition of a table contained both PARTITION and CLUSTER clauses which is illegal. |
| Repair Text: | From Oracle doc: Remove one of the conflicting clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one PARTITION clause may be specified |
| Long Text: | CREATE TABLE statement contained more than one PARTITION clause. |
| Repair Text: | From Oracle doc: Specify PARTITION option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing AT keyword |
| Long Text: | Keyword AT missing. |
| Repair Text: | From Oracle doc: Supply missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GLOBAL partitioned index must be prefixed |
| Long Text: | The partitioning columns of a global partitioned index did not contain a prefix of the index's key columns. |
| Repair Text: | From Oracle doc: Ensure that the GLOBAL partitioned index being created is prefixed and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-existent partitioning column in CREATE TABLE statement |
| Long Text: | Partitioning column specified in CREATE TABLE statement is not one of columns of the table being created. |
| Repair Text: | From Oracle doc: Ensure that all columns in the partitioning column list are columns of the table being created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioning column may not be of type LONG or LONG RAW |
| Long Text: | Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal. |
| Repair Text: | From Oracle doc: Ensure that no partitioning column is of type LONG or LONG RAW. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound of partition number %s is too high |
| Long Text: | High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal. |
| Repair Text: | From Oracle doc: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound value too large for column |
| Long Text: | Length of partition bound value is longer than that of the corresponding partitioning column. |
| Repair Text: | From Oracle doc: Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound of partition "%s" is too high |
| Long Text: | High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal. |
| Repair Text: | From Oracle doc: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GLOBAL partitioned index must be prefixed |
| Long Text: | An attempt was made to create a GLOBAL non-prefixed partitioned index which is illegal. |
| Repair Text: | From Oracle doc: If a non-prefixed index is desired, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioning columns must form a subset of key columns of a UNIQUE index |
| Long Text: | An attempt was made to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal. |
| Repair Text: | From Oracle doc: If you want to create an index whose partitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index's partitioning columns form a subset of its key columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound may not be specified for resulting partitions |
| Long Text: | While parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, partition_description of a resulting partition was found to contain VALUES LESS THAN clause which is illegal. |
| Repair Text: | From Oracle doc: Remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound may not be specified for a partition being moved, modified or rebuilt |
| Long Text: | While parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal. |
| Repair Text: | From Oracle doc: Remove VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one partition may be added |
| Long Text: | ALTER TABLE ADD PARTITION contained descriptions of more than one partition to be added. |
| Repair Text: | From Oracle doc: Ensure that the statement contains exactly one partition definition and that it does not contain any commas. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one partition may be moved |
| Long Text: | ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to be moved. |
| Repair Text: | From Oracle doc: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one partition may be modified |
| Long Text: | ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to be modified. |
| Repair Text: | From Oracle doc: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14046 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a partition may be split into exactly two new partitions |
| Long Text: | ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split. |
| Repair Text: | From Oracle doc: Ensure that the statement describes exactly two partition into which an existing partition is to be split. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14047 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER TABLE|INDEX RENAME may not be combined with other operations |
| Long Text: | ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal. |
| Repair Text: | From Oracle doc: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14048 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a partition maintenance operation may not be combined with other operations |
| Long Text: | The ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (for example, MOVE PARTITION) with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal. |
| Repair Text: | From Oracle doc: Ensure that a partition maintenance operation is the sole operation specified in an ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices, or specifying that a table be renamed (ALTER TABLE RENAME) can be combined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14049 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER TABLE MODIFY PARTITION option |
| Long Text: | An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement for a range or composite range partition. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14050 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER INDEX MODIFY PARTITION option |
| Long Text: | An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14051 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER SNAPSHOT option |
| Long Text: | An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER SNAPSHOT statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition-extended table name syntax is disallowed in this context |
| Long Text: | An attempt was made to use partition-extended table name syntax in illegal context (that is, not in FROM-clause or INSERT, DELETE, or UPDATE statement). |
| Repair Text: | From Oracle doc: Avoid use of partition-extended table name in contexts other those mentioned above. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal attempt to modify %s in %s statement |
| Long Text: | Certain attributes of objects (for example, tables) may be specified at creation time, but may not be modified using ALTER statement. Unfortunately, user specified one of such attributes. |
| Repair Text: | From Oracle doc: Ensure that ALTER statement specifies new values only for attributes which may be changed once an object has been created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER TABLE TRUNCATE PARTITION option |
| Long Text: | Name of the partition to be truncated may be followed by DROP STORAGE or REUSE STORAGE. |
| Repair Text: | From Oracle doc: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14055 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword REBUILD in ALTER INDEX REBUILD must immediately follow index_name |
| Long Text: | ALTER INDEX statement contained REBUILD keyword following some index attributes (for example, INITRANS). |
| Repair Text: | From Oracle doc: Ensure that keyword REBUILD immediately follows the name of the index being altered. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14056 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition number %s: sum of PCTUSED and PCTFREE may not exceed 100 |
| Long Text: | The sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14057 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition "%s": sum of PCTUSED and PCTFREE may not exceed 100 |
| Long Text: | The sum of PCTUSED and PCTFREE for a partition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14058 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition number %s: INITRANS value must be less than MAXTRANS value |
| Long Text: | Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that the value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14059 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition "%s": INITRANS value must be less than MAXTRANS value |
| Long Text: | Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that the value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data type or length of a table partitioning column may not be changed |
| Long Text: | User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition the table named in ALTER TABLE statement, which is illegal. |
| Repair Text: | From Oracle doc: Avoid modifying data type and/or length of table partitioning column(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data type or length of an index partitioning column may not be changed |
| Long Text: | User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition some index defined on the table named in ALTER TABLE statement, which is illegal. |
| Repair Text: | From Oracle doc: Avoid modifying data type and/or length of index partitioning column(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14062 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | one or more of table's partitions reside in a read-only tablespace |
| Long Text: | User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more partitions of which reside in read-only tablespaces, which is illegal. |
| Repair Text: | From Oracle doc: Avoid performing aforementioned operations on a partitioned table one or more partitions of which reside in read-only tablespaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14063 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unusable index exists on unique/primary constraint key |
| Long Text: | An attempt was made to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index marked Index Unusable. |
| Repair Text: | From Oracle doc: Drop the existing index or rebuild it using ALTER INDEX REBUILD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14064 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Index with Unusable partition exists on unique/primary constraint key |
| Long Text: | An attempt was made to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index one or more partitions of which are marked Index Unusable. |
| Repair Text: | From Oracle doc: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14065 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALLOCATE STORAGE may not be specified for a partitioned table |
| Long Text: | User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal. |
| Repair Text: | From Oracle doc: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14066 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal option for a non-partitioned table |
| Long Text: | An attempt was made to issue a CREATE TABLE or ALTER TABLE command on a non-partitioned table, but the command contains an option that is legal only for partitioned tables. Such options are: ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT. |
| Repair Text: | From Oracle doc: Remove the illegal option(s) from the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14067 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate TABLESPACE_NUMBER specification |
| Long Text: | TABLESPACE_NUMBER clause was specified more than once for a table, an index, or an index partition. |
| Repair Text: | From Oracle doc: Correct the code generating text of CREATE INDEX statement sent to the slaves. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14068 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TABLESPACE and TABLESPACE_NUMBER may not be both specified |
| Long Text: | Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, an index, or an index partition. |
| Repair Text: | From Oracle doc: Correct the code generating text of CREATE INDEX statement sent to the slaves. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14069 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid TABLESPACE_NUMBER value |
| Long Text: | The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF. |
| Repair Text: | From Oracle doc: Correct the code generating text of CREATE INDEX statement sent to the slaves. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14070 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | option may be specified only for partitioned indices or with REBUILD |
| Long Text: | User issued ALTER INDEX statement containing an option which is legal only for partitioned indices or in conjunction with REBUILD against a non-partitioned index. Such options are: PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clause. |
| Repair Text: | From Oracle doc: Remove illegal option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for an index used to enforce a constraint |
| Long Text: | An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified for an index used to enforce a constraint. |
| Repair Text: | From Oracle doc: Choose one of the valid index options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14072 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fixed table may not be truncated |
| Long Text: | An attempt was made to truncate a fixed table which is illegal. |
| Repair Text: | From Oracle doc: Ensure that the table being truncated is not a fixed table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14073 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bootstrap table or cluster may not be truncated |
| Long Text: | An attempt was made to truncate a bootstrap table or cluster which is illegal. |
| Repair Text: | From Oracle doc: Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound must collate higher than that of the last partition |
| Long Text: | Partition bound specified in ALTER TABLE ADD PARTITION statement did not collate higher than that of the table's last partition, which is illegal. |
| Repair Text: | From Oracle doc: Ensure that the partition bound of the partition to be added collates higher than that of the table's last partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14075 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition maintenance operations may only be performed on partitioned indices |
| Long Text: | Index named in ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation, at best, meaningless. |
| Repair Text: | From Oracle doc: Ensure that the index named in ALTER INDEX statement specifying a partition maintenance operation is, indeed, partitioned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14076 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DROP/SPLIT PARTITION may not be applied to a LOCAL index partition |
| Long Text: | An attempt was made to drop or split a partition of a LOCAL index which is illegal. |
| Repair Text: | From Oracle doc: Ensure that the index named in such statement is a GLOBAL partitioned index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | you may not drop the highest partition of a GLOBAL index |
| Long Text: | An attempt was made to drop highest partition of a GLOBAL index, which is illegal. |
| Repair Text: | From Oracle doc: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14079 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal option for a partition marked Index Unusable |
| Long Text: | ALTER INDEX MODIFY PARTITION statement against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal. |
| Repair Text: | From Oracle doc: Ensure that only valid options are specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14080 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition cannot be split along the specified high bound |
| Long Text: | An attempt was made to split a partition along a bound which either collates higher than that of the partition to be split or lower than that of a partition immediately preceding the one to be split. |
| Repair Text: | From Oracle doc: Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher that of a partition immediately preceding the one to be split. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14081 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new partition name must differ from the old partition name |
| Long Text: | User entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of the partition being renamed. |
| Repair Text: | From Oracle doc: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new partition name must differ from that of any other partition of the object |
| Long Text: | User entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of some existing partition of the object. |
| Repair Text: | From Oracle doc: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14083 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop the only partition of a partitioned table |
| Long Text: | A drop partition command is being executed when there is only one partition in the table. |
| Repair Text: | From Oracle doc: Ensure that there is at least one partition. Drop table to remove all partitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | you may specify TABLESPACE DEFAULT only for a LOCAL index |
| Long Text: | An attempt was made to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal. |
| Repair Text: | From Oracle doc: Re-enter the statement without TABLESPACE DEFAULT clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14085 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned table cannot have column with LONG datatype |
| Long Text: | An attempt was made to create a partitioned table with a LONG datatype or tried to add a LONG datatype column to a partitioned table. |
| Repair Text: | From Oracle doc: LONG data types are not supported with partitioned tables. Create table without LONG column or change table to not partitioned. If adding column, do not use LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non-partitioned table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14086 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a partitioned index may not be rebuilt as a whole |
| Long Text: | An attempt was made to rebuild a partitioned index using ALTER INDEX REBUILD statement, which is illegal. |
| Repair Text: | From Oracle doc: Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and re-create the entire index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14094 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER TABLE EXCHANGE PARTITION option |
| Long Text: | Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEXES][{WITH|WITHOUT} VALIDATION]. |
| Repair Text: | From Oracle doc: Ensure that no options besides INCLUDING INDEXES or EXCLUDING INDEXES are specified with ALTER TABLE EXCHANGE PARTITION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14095 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table |
| Long Text: | The table in the EXCHANGE operation is either clustered or partitioned. |
| Repair Text: | From Oracle doc: Ensure that the table with which the partition is being exchanged for is not partitioned or clustered. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14096 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns |
| Long Text: | The two tables specified in the EXCHANGE have different number of columns. |
| Repair Text: | From Oracle doc: Ensure that the two tables have the same number of columns with the same type and size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14097 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column type or size mismatch in ALTER TABLE EXCHANGE PARTITION |
| Long Text: | The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size. |
| Repair Text: | From Oracle doc: Ensure that the two tables have the same number of columns with the same type and size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14098 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index mismatch for tables in ALTER TABLE EXCHANGE PARTITION |
| Long Text: | The two tables specified in the EXCHANGE have indexes which are not equivalent. |
| Repair Text: | From Oracle doc: Ensure that the indexes for the two tables have indexes which follow this rule For every non-partitioned index for the non-partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14099 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | all rows in table do not qualify for specified partition |
| Long Text: | There is at least one row in the non-partitioned table which does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION. |
| Repair Text: | From Oracle doc: Ensure that all the rows in the segment qualify for the partition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition extended table name cannot refer to a remote object |
| Long Text: | An attempt was made to use partition-extended table name syntax in conjunction with remote object name which is illegal. |
| Repair Text: | From Oracle doc: Correct the statement and re-enter it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition extended table name cannot refer to a synonym |
| Long Text: | An attempt was made to use partition-extended table name syntax in conjunction with synonym name which is illegal. |
| Repair Text: | From Oracle doc: Correct the statement and re-enter it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one LOGGING or NOLOGGING clause may be specified |
| Long Text: | LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified. |
| Repair Text: | From Oracle doc: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE |
| Long Text: | A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is disallowed. |
| Repair Text: | From Oracle doc: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14104 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices |
| Long Text: | CREATE TABLE/INDEX statement used to create a partitioned table/index contained RECOVERABLE or UNRECOVERABLE clause which is illegal. |
| Repair Text: | From Oracle doc: Remove offending clause. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RECOVERABLE/UNRECOVERABLE may not be specified in this context |
| Long Text: | RECOVERABLE/UNRECOVERABLE clause is not allowed in this context. |
| Repair Text: | From Oracle doc: Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOGGING/NOLOGGING may not be specified for a clustered table |
| Long Text: | An attempt was made to specify LOGGING or NOLOGGING clause in CREATE TABLE or ALTER TABLE statement involving a clustered table. |
| Repair Text: | From Oracle doc: Remove offending clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition specification is required for a partitioned object |
| Long Text: | parameter which supplies partition name is missing. This parameter is optional for non-partitioned objects, but is required for partitioned objects. |
| Repair Text: | From Oracle doc: Supply the missing parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal partition-extended table name syntax |
| Long Text: | Partition to be accessed may only be specified using its name. An attempt was made to use a partition number or a bind variable. |
| Repair Text: | From Oracle doc: Modify the statement to refer to a partition using its name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition-extended object names may only be used with tables |
| Long Text: | An attempt was made to use a partition-extended object name with an object which is not a table. |
| Repair Text: | From Oracle doc: Avoid using partition-extended name syntax with objects which are not tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioning column may not be of type ROWID |
| Long Text: | Partitioning column specified by the user was of type ROWID, which is illegal. |
| Repair Text: | From Oracle doc: Ensure that no partitioning column is of type ROWID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | creation of GLOBAL partitioned indices on clustered tables is not supported |
| Long Text: | An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal. |
| Repair Text: | From Oracle doc: Remove PARTITION BY RANGE() clause along with (partition_list) to create a GLOBAL non-partitioned index on a clustered table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition |
| Long Text: | Description of a partition or subpartition found in CREATE TABLE/INDEX statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal. |
| Repair Text: | From Oracle doc: Remove offending clause. Use LOGGING or NOLOGGING instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned table cannot have column with LOB datatype |
| Long Text: | An attempt was made to create a partitioned table with a LOB datatype or tried to add a LOB datatype column to a partitioned table. |
| Repair Text: | From Oracle doc: LOB data types are not supported with partitioned tables. Create table without LOB column or change table to not partitioned. If adding column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non-partitioned table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned table cannot have column with object, REF, nested table, array datatype |
| Long Text: | An attempt was made to create a partitioned table with a object datatype (object, REF, nested table, array) or tried to add a object datatype column to a partitioned table. |
| Repair Text: | From Oracle doc: object data types are not supported with partitioned tables. Create table without object column or change table to not partitioned. If adding column, do not use object datatypes. If modifying attributes of a column to change data type to object, it has to be a non-partitioned table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound of partition number %s is too long |
| Long Text: | Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K). |
| Repair Text: | From Oracle doc: Change representation of a partition high bound to bring its length within legal limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound of partition "%s" is too long |
| Long Text: | Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K). |
| Repair Text: | From Oracle doc: Change representation of a partition high bound to bring its length within legal limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14117 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition resides in offlined tablespace |
| Long Text: | User attempted an operation requiring that we access data in a partition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. |
| Repair Text: | From Oracle doc: Bring the tablespace online before attempting the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14118 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION |
| Long Text: | The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint defined on them. |
| Repair Text: | From Oracle doc: Ensure that the two tables do not have CHECK constraint defined on any column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14119 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified partition bound is too long |
| Long Text: | Length of a linear key representation of a high bound of a table partition being added or along which an existing table or index partition is being split exceeded the legal limit (4K). |
| Repair Text: | From Oracle doc: Change representation of a partition high bound to bring its length within legal limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incompletely specified partition bound for a DATE column |
| Long Text: | An attempt was made to use a date expression whose format does not fully (that is, day, month, and year (including century)) specify a date as a partition bound for a DATE column. The format may have been specified explicitly (using TO_DATE() function) or implicitly (NLS_DATE_FORMAT). |
| Repair Text: | From Oracle doc: Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (that is, day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (that is, including the century) specification of the year, use TO_DATE() (for example, TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully express the desired date. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MODIFY DEFAULT ATTRIBUTES may not be combined with other operations |
| Long Text: | ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal. |
| Repair Text: | From Oracle doc: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one REVERSE or NOREVERSE clause may be specified |
| Long Text: | Both REVERSE and NOREVERSE were specified in CREATE INDEX statement. |
| Repair Text: | From Oracle doc: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate NOREVERSE clause |
| Long Text: | NOREVERSE was specified more than once in ALTER INDEX statement. |
| Repair Text: | From Oracle doc: Remove all but one of the NOREVERSE clauses and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate REVERSE clause |
| Long Text: | REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements. |
| Repair Text: | From Oracle doc: Remove all but one of the REVERSE clauses and reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REVERSE/NOREVERSE may not be specified in this context |
| Long Text: | REVERSE/NOREVERSE clause is not allowed in this context. |
| Repair Text: | From Oracle doc: Remove offending clause. REVERSE may be specified as an attribute of an index (not of an individual partition, if creating a partitioned index) in CREATE INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be specified only in ALTER INDEX REBUILD statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only a parallel_clause may follow description(s) of resulting partitions |
| Long Text: | Descriptions of partition(s) resulting from splitting of a table or index partition may be followed by an optional parallel_clause which applies to the entire statement and which, in turn, may not be followed by any other clause. |
| Repair Text: | From Oracle doc: Ensure that all partition attributes appear within the parenthesized list of descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION |
| Long Text: | The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints. |
| Repair Text: | From Oracle doc: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14129 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints |
| Long Text: | Matching UNIQUE constraints in both table are enabled and validated but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command. |
| Repair Text: | From Oracle doc: Disable currently enabled matching UNIQUE constraints on both tables or ensure that INCLUDING INDEXES option is used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14130 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION |
| Long Text: | One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated. |
| Repair Text: | From Oracle doc: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE PARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14131 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enabled UNIQUE constraint exists on one of the tables |
| Long Text: | One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which prevents EXCHANGE from proceeding. |
| Repair Text: | From Oracle doc: Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14132 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table cannot be used in EXCHANGE |
| Long Text: | An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but the non-partitioned table cannot be used in the EXCHANGE because one or more of the following apply: it is a typed table it contains ADT columns it contains nested-table columns it contains REF columns it contains array columns it is an index-organized table it contains LOB columns it is a nested table |
| Repair Text: | From Oracle doc: Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14133 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER TABLE MOVE cannot be combined with other operations |
| Long Text: | An attempt was made to combine an ALTER TABLE MOVE statement with another operation, such as MODIFY. |
| Repair Text: | From Oracle doc: Make sure that MOVE is the only operation specified in ALTER TABLE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14134 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | indexes cannot use both DESC and REVERSE |
| Long Text: | An attempt was made to make a reverse index with some index columns marked DESC. |
| Repair Text: | From Oracle doc: Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes backwards, which allows a normal reverse index to simulate a reverse index with columns marked DESC. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14135 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a LOB column cannot serve as a partitioning column |
| Long Text: | An attempt was made to specify a column of type BLOB or CLOB as a partitioning or subpartitioning column. |
| Repair Text: | From Oracle doc: Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing SUBPARTITION keyword |
| Long Text: | Keyword SUBPARTITION missing. |
| Repair Text: | From Oracle doc: Supply the missing parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid table partitioning method |
| Long Text: | Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, HASH, or composite range/hash (R+H). |
| Repair Text: | From Oracle doc: Specify one of valid partitioning methods. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number of partitions specified in PARTITIONS clause |
| Long Text: | number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of partitions outside of legal range (1-65535). |
| Repair Text: | From Oracle doc: Specify a number between 1 and 65535 in the number-of-partitions clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one of STORE IN or partition_description clause may be specified |
| Long Text: | Both STORE IN and partition_description clauses were specified in a CREATE TABLE|INDEX command. |
| Repair Text: | From Oracle doc: Remove one of offending clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14154 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one of STORE IN or subpartition_description clause may be specified |
| Long Text: | Both STORE IN and subpartition_description clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS command for a composite range-partitioned object. |
| Repair Text: | From Oracle doc: Remove one of offending clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing PARTITION or SUBPARTITION keyword |
| Long Text: | Expected either the PARTITION or SUBPARTITION keyword but neither was supplied. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14156 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid number of subpartitions specified in SUBPARTITIONS clause |
| Long Text: | Number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside of legal range (1-65535). |
| Repair Text: | From Oracle doc: Specify a number between 1 and 65535 in the number-of-subpartitions clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14157 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid subpartition name |
| Long Text: | A subpartition name of the form identifier is expected but not present. |
| Repair Text: | From Oracle doc: Enter an appropriate subpartition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14158 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many subpartition descriptions |
| Long Text: | CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; maximum number of subpartitions is 65535. |
| Repair Text: | From Oracle doc: Reduce the number of subpartitions to not exceed 65535. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14159 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate subpartition name |
| Long Text: | Name of a subpartition of a table or index being created is not unique. |
| Repair Text: | From Oracle doc: Rename the subpartition(s) to ensure that their names are unique among subpartitions of the table or index being created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this physical attribute may not be specified for a table subpartition |
| Long Text: | An unexpected option was encountered while parsing physical attributes of a table subpartition; TABLESPACE is the only valid option. |
| Repair Text: | From Oracle doc: Remove the invalid option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition number %s: sum of PCTUSED and PCTFREE may not exceed 100 |
| Long Text: | The sum of PCTUSED and PCTFREE for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition "%s": sum of PCTUSED and PCTFREE may not exceed 100 |
| Long Text: | The sum of PCTUSED and PCTFREE for a subpartition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition number %s: INITRANS value must be less than MAXTRANS value |
| Long Text: | The value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14164 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition "%s": INITRANS value must be less than MAXTRANS value |
| Long Text: | The value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. |
| Repair Text: | From Oracle doc: Ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14165 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations |
| Long Text: | An ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal. |
| Repair Text: | From Oracle doc: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14166 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing INTO keyword |
| Long Text: | Keyword INTO missing. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14167 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one subpartition may be moved |
| Long Text: | ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one subpartition to be moved. |
| Repair Text: | From Oracle doc: Ensure that the statement describes exactly one subpartition to be moved and that it does not contain any commas. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14168 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one subpartition may be modified |
| Long Text: | ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one subpartition to be modified. |
| Repair Text: | From Oracle doc: Ensure that the statement describes exactly one subpartition to be modified and that it does not contain any commas. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14169 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER TABLE MODIFY SUBPARTITION option |
| Long Text: | An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14170 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify partition_description clause in CREATE TABLE|INDEX |
| Long Text: | User requested to generate default partition description(s) (possibly via PARTITIONS number_of_partitions) while at the same time specified partition_description clause which is illegal. |
| Repair Text: | From Oracle doc: Remove one of offending clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14171 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify subpartition_description clause in CREATE|ALTER TABLE |
| Long Text: | User requested to generate default subpartition description(s) (possibly via SUBPARTITIONS) while at the same time specified subpartition_description clause which is illegal. |
| Repair Text: | From Oracle doc: Remove one of offending clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14172 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER TABLE EXCHANGE SUBPARTITION option |
| Long Text: | Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]. |
| Repair Text: | From Oracle doc: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14173 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal subpartition-extended table name syntax |
| Long Text: | Subpartition to be accessed may only be specified using its name. An attempt was made to use a subpartition number or a bind variable. |
| Repair Text: | From Oracle doc: Modify statement to refer to a subpartition using its name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14174 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only a parallel_clause may follow COALESCE PARTITION|SUBPARTITION |
| Long Text: | ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional parallel_clause. No partition/subpartition attributes may be specified. |
| Repair Text: | From Oracle doc: Ensure that no partition/subpartition attribute was specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14175 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a subpartition maintenance operation may not be combined with other operations |
| Long Text: | An ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (for example, MOVE SUBPARTITION) with some other operation (for example, MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal. |
| Repair Text: | From Oracle doc: Ensure that a subpartition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14176 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this attribute may not be specified for a hash partition |
| Long Text: | An invalid option was encountered while parsing physical attributes of a partition of a table partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions. |
| Repair Text: | From Oracle doc: Remove the invalid option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14183 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TABLESPACE DEFAULT can be specified only for Composite LOCAL index |
| Long Text: | An attempt was made to specify TABLESPACE DEFAULT for a partition of a range/system/hash-partitioned LOCAL index object, which is illegal. |
| Repair Text: | From Oracle doc: Replace TABLESPACE DEFAULT with TABLESPACE ts_name or remove it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14185 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect physical attribute specified for this index partition |
| Long Text: | An unexpected option was encountered while parsing physical attributes of a local index partition; valid options for range composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING and TABLESPACE; but only TABLESPACE may be specified for hash partitions STORE IN () is also disallowed for all but composite range partitions. |
| Repair Text: | From Oracle doc: Remove the invalid option(s) from the list of physical attributes of an index partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14186 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of sub-partitions of LOCAL index must equal that of the underlying table |
| Long Text: | An attempt was made to create a LOCAL partitioned index with a number of subpartitions which is different from that of the underlying table. |
| Repair Text: | From Oracle doc: Correct the CREATE INDEX statement to specify a correct number of subpartitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14187 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioning method for LOCAL index is inconsistent with that of the underlying table |
| Long Text: | An attempt was made to create a LOCAL partitioned index that is not equipartitioned with the underlying table. The partitioning types are mismatched. |
| Repair Text: | From Oracle doc: Correct the CREATE INDEX statement to ensure that the index partitioning method is consistent with that of the base table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14188 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sub-partitioning columns must form a subset of key columns of a UNIQUE index |
| Long Text: | An attempt was made to create a UNIQUE partitioned index whose subpartitioning columns do not form a subset of its key columns which is illegal. |
| Repair Text: | From Oracle doc: If you want to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioning columns to ensure that the index's subpartitioning columns form a subset of its key columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14189 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this physical attribute may not be specified for an index subpartition |
| Long Text: | An unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option. |
| Repair Text: | From Oracle doc: Remove the invalid option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14190 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one ENABLE/DISABLE ROW MOVEMENT clause can be specified |
| Long Text: | One of the following: ENABLE ROW MOVEMENT was specified more than once. DISABLE ROW MOVEMENT was specified more than once. Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were specified. |
| Repair Text: | From Oracle doc: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses and then reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14191 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALLOCATE STORAGE may not be specified for Composite Range partitioned object |
| Long Text: | User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal. |
| Repair Text: | From Oracle doc: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14192 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify physical index attributes of a Hash index partition |
| Long Text: | An attempt was made to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an index partition of a hash-partitioned index. |
| Repair Text: | From Oracle doc: Remove the physical attributes one is trying to modify. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14193 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER INDEX MODIFY SUBPARTITION option |
| Long Text: | An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14194 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one subpartition may be rebuilt |
| Long Text: | ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt. |
| Repair Text: | From Oracle doc: Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14195 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALLOCATE STORAGE may not be specified for RANGE partitioned object |
| Long Text: | User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal. |
| Repair Text: | From Oracle doc: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Specified subpartition does not exist |
| Long Text: | Subpartition not found for the object. |
| Repair Text: | From Oracle doc: Retry with correct subpartition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14252 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ALTER TABLE MODIFY PARTITION option for a Hash partition |
| Long Text: | Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a hash partition. |
| Repair Text: | From Oracle doc: Specify only legal options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14253 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table is not partitioned by Composite Range method |
| Long Text: | The table in a subpartition maintenance operation (ALTER TABLE EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION ADD/COALESCE SUBPARTITION command must be partitioned by composite range method. |
| Repair Text: | From Oracle doc: Ensure that the table is partitioned by composite range method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14254 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify ALLOCATE STORAGE for a (Composite) Range partitioned table |
| Long Text: | User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a range or composite range partitioned table which is illegal. |
| Repair Text: | From Oracle doc: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14255 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table is not partitioned by Range or Composite Range method |
| Long Text: | ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by range or composite range method. |
| Repair Text: | From Oracle doc: Ensure that the table is partitioned by range or composite range method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14256 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid resulting partition description(s) |
| Long Text: | User specified STORE-IN clause, SUBPARTITIONS clause, and/or subpartition_description clause in partition description(s) in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the maintenance operation is not a composite range-partitioned table which is illegal. |
| Repair Text: | From Oracle doc: Remove the invalid clause(s), or ensure that the table is partitioned by composite range method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14257 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot move partition other than a Range or Hash partition |
| Long Text: | An attempt was made to move a partition that is not a range or hash partition which is illegal. |
| Repair Text: | From Oracle doc: Specify MOVE PARTITION for a range or hash partition only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14258 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid partition description |
| Long Text: | User specified STORE-IN clause, SUBPARTITIONS clause, and/or subpartition_description clause in ALTER TABLE ADD PARTITION statement but the table in the maintenance operation is not a composite range/hash-partitioned table which is illegal. |
| Repair Text: | From Oracle doc: Remove the invalid clause(s), or ensure that the table is partitioned by composite range/hash method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14259 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table is not partitioned by Hash method |
| Long Text: | ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method. |
| Repair Text: | From Oracle doc: Specify a valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14260 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect physical attribute specified for this partition |
| Long Text: | User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and/or [NO]LOGGING option to a hash partition via ALTER TABLE ADD/MOVE PARTITION command which is illegal. Only TABLESPACE may be specified. |
| Repair Text: | From Oracle doc: Remove the invalid option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound may not be specified when adding this Hash partition |
| Long Text: | User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a hash-partitioned table which is illegal. |
| Repair Text: | From Oracle doc: Remove the VALUES LESS THAN clause from the description of partition being added. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new subpartition name must differ from the old subpartition name |
| Long Text: | User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of the subpartition being renamed. |
| Repair Text: | From Oracle doc: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new subpartition name must differ from that of any other subpartition of the object |
| Long Text: | User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of some existing subpartition of the object. |
| Repair Text: | From Oracle doc: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14264 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table is not partitioned by Composite Range method |
| Long Text: | The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method. |
| Repair Text: | From Oracle doc: Ensure that the table is partitioned by Composite method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14265 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data type or length of a table subpartitioning column may not be changed |
| Long Text: | User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition the table named in ALTER TABLE statement, which is illegal. |
| Repair Text: | From Oracle doc: Avoid modifying data type and/or length of table subpartitioning column(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14266 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data type or length of an index subpartitioning column may not be changed |
| Long Text: | User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition some index defined on the table named in ALTER TABLE statement, which is illegal. |
| Repair Text: | From Oracle doc: Avoid modifying data type and/or length of index subpartitioning column(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14267 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify PARALLEL clause when adding a (Composite) Range partition |
| Long Text: | User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a range or composite range partition which is illegal. |
| Repair Text: | From Oracle doc: Remove the PARALLEL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14268 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition '%s' of the partition resides in offlined tablespace |
| Long Text: | User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. |
| Repair Text: | From Oracle doc: Bring tablespace online before attempting the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14269 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot exchange partition other than a Range or Hash partition |
| Long Text: | User attempt to exchange a partition with a non-partitioned table but the specified partition is not a range or hash partition which is illegal. |
| Repair Text: | From Oracle doc: Specify EXCHANGE PARTITION for a range or hash partition only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table is not partitioned by Range or Hash method |
| Long Text: | The table in ALTER TABLE MODIFY PARTITION {UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES} statement is not partitioned by range or hash method which is illegal. |
| Repair Text: | From Oracle doc: Ensure that the table is partitioned by range or hash method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table is not partitioned by Composite Range/Hash method |
| Long Text: | The table in ALTER TABLE MODIFY SUBPARTITION {UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES} statement is not partitioned by composite range/hash method which is illegal. |
| Repair Text: | From Oracle doc: Ensure that the table is partitioned by composite range/hash method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14272 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only a partition with higher bound can be reused |
| Long Text: | User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal. |
| Repair Text: | From Oracle doc: Use the higher-bound partition to be the resulting partition or specify a new partition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14273 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | lower-bound partition must be specified first |
| Long Text: | User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal. |
| Repair Text: | From Oracle doc: Specify lower-bound partition then higher-bound partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14274 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitions being merged are not adjacent |
| Long Text: | User attempt to merge two partitions that are not adjacent to each other which is illegal. |
| Repair Text: | From Oracle doc: Specify two partitions that are adjacent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14275 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot reuse lower-bound partition as resulting partition |
| Long Text: | User attempt to reuse lower-bound partition of the partitions being merged which is illegal. |
| Repair Text: | From Oracle doc: Specify new resulting partition name or reuse the higher-bound partition only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table |
| Long Text: | The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned. |
| Repair Text: | From Oracle doc: Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tables in EXCHANGE SUBPARTITION must have the same number of columns |
| Long Text: | The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns. |
| Repair Text: | From Oracle doc: Ensure that the two tables have the same number of columns with the same type and size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column type or size mismatch in EXCHANGE SUBPARTITION |
| Long Text: | The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION are of different type or size. |
| Repair Text: | From Oracle doc: Ensure that the two tables have the same number of columns with the same type and size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14279 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION |
| Long Text: | The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have indexes which are not equivalent. |
| Repair Text: | From Oracle doc: Ensure that the indexes for the two tables have indexes which follow this rule For every non-partitioned index for the non-partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14280 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | all rows in table do not qualify for specified subpartition |
| Long Text: | There is at least one row in the non-partitioned table which does not qualify for the subpartition specified in the ALTER TABLE EXCHANGE SUBPARTITION. |
| Repair Text: | From Oracle doc: Ensure that all the rows in the segment qualify for the subpartition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that subpartition to find out the invalid rows and delete them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION |
| Long Text: | The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint defined on them. |
| Repair Text: | From Oracle doc: Ensure that the two tables do not have CHECK constraint defined on any column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14282 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION |
| Long Text: | The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints. |
| Repair Text: | From Oracle doc: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14283 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION |
| Long Text: | One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated. |
| Repair Text: | From Oracle doc: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14284 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | one or more of table's subpartitions reside in a read-only tablespace |
| Long Text: | User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more subpartitions of which reside in read-only tablespaces, which is illegal. |
| Repair Text: | From Oracle doc: Avoid performing aforementioned operations on a partitioned table one or more subpartitions of which reside in read-only tablespaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14285 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot COALESCE the only partition of this partitioned table |
| Long Text: | A COALESCE PARTITION command was issued when there is only one partition in the table which is illegal. |
| Repair Text: | From Oracle doc: Ensure that there is at least one partition. Drop table to remove all partitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14286 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot COALESCE the only subpartition of this table partition |
| Long Text: | A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition which is illegal. |
| Repair Text: | From Oracle doc: Ensure that there is at least one subpartition. Drop partition to remove all subpartitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14287 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot REBUILD a partition of a Composite Range partitioned index |
| Long Text: | An attempt was made to rebuild a partition of a composite range-partitioned index which is illegal. |
| Repair Text: | From Oracle doc: REBUILD the index partition, a subpartition at a time. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14288 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | index is not partitioned by Composite Range method |
| Long Text: | The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or ALTER INDEX REBUILD SUBPARTITION command must be partitioned by composite range method. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14289 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot make local index partition of Composite Range partitioned table unusable |
| Long Text: | An attempt was made to rebuild a partition of a composite range partitioned index which is illegal. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION |
| Long Text: | The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints. |
| Repair Text: | From Oracle doc: Ensure that the two tables do not have PRIMARY KEY constraints defined on any column or disable all PRIMARY KEY constraints on both tables. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14291 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot EXCHANGE a composite partition with a non-partitioned table |
| Long Text: | A composite partition can only be exchanged with a partitioned table. |
| Repair Text: | From Oracle doc: Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14292 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Partitioning type of table must match subpartitioning type of composite partition |
| Long Text: | When exchanging a partitioned table with a composite partition, the partitioning type of the table must match the subpartitioning type of the composite partition. |
| Repair Text: | From Oracle doc: Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14293 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Number of partitioning columns does not match number of subpartitioning columns |
| Long Text: | When exchanging a partitioned table with a composite partition, the number of partitioning columns of the table must match the number of subpartitioning columns of the composite partition. |
| Repair Text: | From Oracle doc: Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the composite partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14294 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Number of partitions does not match number of subpartitions |
| Long Text: | When exchanging a partitioned table with a composite partition, the number of partitions of the table must match the number of subpartitions of the composite partition. |
| Repair Text: | From Oracle doc: Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14295 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column type or size mismatch between partitioning columns and subpartitioning columns |
| Long Text: | When exchanging a partitioned table with a composite partition, the type and size of the partitioning columns of the table must match the type and size of the subpartitioning columns of the composite partition. |
| Repair Text: | From Oracle doc: Ensure that the type and size of the partitioning columns of the partitioned is the same as the type and size of the subpartitioning columns of the composite partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table-level attributes must be specified before partition-level attributes |
| Long Text: | While processing an ALTER TABLE ADD COLUMN statement, table-level attributes of LOB columns were encountered after processing partition-level attributes of LOB columns or while processing CREATE TABLE statement, table-level attributes of LOB columns were encountered after processing partition descriptions. |
| Repair Text: | From Oracle doc: Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one list of added-LOB-storage-clauses can be specified in a statement |
| Long Text: | While parsing an ALTER TABLE ADD COLUMN statement, one list of added-LOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was encountered. There cannot be more than one list of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must be combined into one list. |
| Repair Text: | From Oracle doc: Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitions or subpartitions are not in the right order |
| Long Text: | Descriptions of partitions or subpartitions in an ALTER TABLE ADD COLUMN statement were ordered differently from the DDL order of partitions or subpartitions. |
| Repair Text: | From Oracle doc: Re-order the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inserted partition key is beyond highest legal partition key |
| Long Text: | At attempt was made to insert a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition. |
| Repair Text: | From Oracle doc: Do not insert the key. Or, add a partition capable of accepting the key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inserted partition key is outside specified partition |
| Long Text: | The concatenated partition key of an inserted record is outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement. |
| Repair Text: | From Oracle doc: Do not insert the key or insert it in another partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | updating partition key column would cause a partition change |
| Long Text: | An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition. |
| Repair Text: | From Oracle doc: Do not attempt to update a partition key column or make sure that the new partition key is within the range containing the old partition key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14403 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cursor invalidation detected after getting DML partition lock |
| Long Text: | Cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned table contains partitions in a different tablespace |
| Long Text: | An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace. |
| Repair Text: | From Oracle doc: Find tables with partitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move partitions to a different tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14405 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned index contains partitions in a different tablespace |
| Long Text: | An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace. |
| Repair Text: | From Oracle doc: Find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | updated partition key is beyond highest legal partition key |
| Long Text: | At attempt was made to update a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition. |
| Repair Text: | From Oracle doc: Do not update the key. Or, add a partition capable of accepting the key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned table contains subpartitions in a different tablespace |
| Long Text: | An attempt was made to drop a tablespace which contains tables whose subpartitions are not completely contained in this tablespace. |
| Repair Text: | From Oracle doc: Find tables with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move subpartitions to a different tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioned index contains subpartitions in a different tablespace |
| Long Text: | An attempt was made to drop a tablespace which contains indexes whose subpartitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace. |
| Repair Text: | From Oracle doc: Find indexes with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14409 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inserted partition key is outside specified subpartition |
| Long Text: | The concatenated partition key of an inserted record is outside the ranges of the two concatenated subpartition bound lists that delimit the subpartition named in the INSERT statement. |
| Repair Text: | From Oracle doc: Do not insert the key or insert it in another subpartition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14450 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to access a transactional temp table already in use |
| Long Text: | An attempt was made to access a transactional temporary table that has been already populated by a concurrent transaction of the same session. |
| Repair Text: | From Oracle doc: Do not attempt to access the temporary table until the concurrent transaction has committed or aborted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14451 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | unsupported feature with temporary table |
| Long Text: | An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to create, alter or drop an index on temporary table already in use |
| Long Text: | An attempt was made to create, alter or drop an index on temporary table which is already in use. |
| Repair Text: | From Oracle doc: All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to use a LOB of a temporary table, whose data has already been purged |
| Long Text: | An attempt was made to use LOB from a temporary table whose data has been dropped either because table was transaction-specific and transaction has committed or aborted, table was truncated or session which created this LOB has ended. |
| Repair Text: | From Oracle doc: This LOB locator is invalid and cannot be used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14454 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to reference temporary table in a referential integrity constraint |
| Long Text: | An attempt was made to reference temporary table in a referential integrity constraint. This is not supported. |
| Repair Text: | From Oracle doc: Use triggers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14455 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to create referential integrity constraint on temporary table |
| Long Text: | An attempt was made to create a referential integrity constraint on a temporary table. This is not supported. |
| Repair Text: | From Oracle doc: Use triggers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14456 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot rebuild index on a temporary table |
| Long Text: | An attempt was made to rebuild an index on a temporary table. |
| Repair Text: | From Oracle doc: The index data is anyway lost at end of session/transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14457 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | disallowed VARRAY and Nested Table column in a Temporary table |
| Long Text: | An attempt made to create a VARRAY or Nested Table column in a temporary table. This is not supported. |
| Repair Text: | From Oracle doc: Do not specify these datatypes for temporary tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14458 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt was made to create a temporary table with INDEX organization |
| Long Text: | An attempt was made to create an Index Organized Temporary table. This is not supported. |
| Repair Text: | From Oracle doc: Create the table with HEAP organization and the primary key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14459 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing GLOBAL keyword |
| Long Text: | Keyword GLOBAL is missing while creating temporary table. |
| Repair Text: | From Oracle doc: Supply the missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOCAL option not valid without partition name |
| Long Text: | Incorrect syntax specified. |
| Repair Text: | From Oracle doc: Retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object is not partitioned |
| Long Text: | Table or index is not partitioned. Invalid syntax. |
| Repair Text: | From Oracle doc: Retry the command with correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one partition name can be specified |
| Long Text: | More than one partition name has been specified for analyze. |
| Repair Text: | From Oracle doc: Specify one partition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax not supported for analyze |
| Long Text: | A partition/subpartition number or bind variable has been used. |
| Repair Text: | From Oracle doc: Specify a valid partition/subpartition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOCAL option valid only for partitioned indexes |
| Long Text: | Incorrect syntax specified. |
| Repair Text: | From Oracle doc: Retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOCAL option required for partitioned indexes |
| Long Text: | Incorrect syntax specified. |
| Repair Text: | From Oracle doc: Retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition corrupt. all rows do not fall within partition bounds |
| Long Text: | The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation. |
| Repair Text: | From Oracle doc: Delete rows in partition which do not qualify. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified VALIDATE INTO table not found |
| Long Text: | The specified table either does not exist or user does not have the proper privileges. |
| Repair Text: | From Oracle doc: Specify the correct table to use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified VALIDATE INTO table form incorrect |
| Long Text: | The specified table does not have the proper field definitions. |
| Repair Text: | From Oracle doc: Specify the correct table to use. See UTLVALID.SQL for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can specify VALIDATE INTO clause only for partitioned tables |
| Long Text: | The VALIDATE INTO has been specified for a non-partitioned table or cluster or index. |
| Repair Text: | From Oracle doc: Use the syntax correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform operation on a partitioned object |
| Long Text: | An attempt was made to perform an operation that is not allowed on partitioned tables or indexes. |
| Repair Text: | From Oracle doc: Retry the command with correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform operation on a clustered object |
| Long Text: | An attempt was made to perform an operation that is not allowed on clustered tables or indexes. |
| Repair Text: | From Oracle doc: Retry the command with correct syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioning column may not be of object datatype |
| Long Text: | Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal. |
| Repair Text: | From Oracle doc: Ensure that no partitioning column is an object datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOCAL option not valid without subpartition name |
| Long Text: | Incorrect syntax specified. |
| Repair Text: | From Oracle doc: Retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14515 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one aubpartition name can be specified |
| Long Text: | More than one subpartition name has been specified for analyze. |
| Repair Text: | From Oracle doc: Specify one subpartition name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14516 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition corrupt. all rows do not fall within subpartition bounds |
| Long Text: | The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation. |
| Repair Text: | From Oracle doc: Delete rows in subpartition which do not qualify. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14517 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition of index '%s.%s' is in unusable state |
| Long Text: | An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation. |
| Repair Text: | From Oracle doc: REBUILD the unusable index subpartition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform a DML operation inside a query |
| Long Text: | DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave. |
| Repair Text: | From Oracle doc: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform a DDL, commit or rollback inside a query or DML |
| Long Text: | DDL operations like creation tables, views etc. and transaction control statements such as commit/rollback cannot be performed inside a query or a DML statement. |
| Repair Text: | From Oracle doc: Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-14553 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform a lob write operation inside a query |
| Long Text: | A LOB write operation cannot be performed inside a query or a PDML slave. |
| Repair Text: | From Oracle doc: Ensure that the offending LOB write operation is not performed or use an autonomous transaction to perform the operation within the query or PDML slave. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database open for read-only access |
| Long Text: | The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error. |
| Repair Text: | From Oracle doc: In order to modify the database, it must first be shut down and reopened for read-write access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database already open for read-only access by another instance |
| Long Text: | The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance. |
| Repair Text: | From Oracle doc: This instance must be opened for read-write access, or all other instances must first be shut down and reopened for read-only access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database already open for read-write access by another instance |
| Long Text: | The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance. |
| Repair Text: | From Oracle doc: This instance must be opened for read-only access, or all other instances must first be shut down and reopened for read-write access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby database is restricted to read-only access |
| Long Text: | To ensure its integrity, a standby database can only be opened for read-only access. |
| Repair Text: | From Oracle doc: Re-issue the ALTER DATABASE OPEN specifying READ ONLY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | backup database requires recovery |
| Long Text: | The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance. |
| Repair Text: | From Oracle doc: Perform the necessary recovery and re-open for read-only access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database requires recovery |
| Long Text: | The database requires recovery, and therefore cannot be opened for read-only access by this instance. |
| Repair Text: | From Oracle doc: Perform the necessary recovery and re-open for read-only access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | audit_trail destination incompatible with database open mode |
| Long Text: | The AUDIT_TRAIL initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access. |
| Repair Text: | From Oracle doc: When the database is opened for read-only access, the AUDIT_TRAIL initialization parameter can only be set to "OS" or "NONE" (FALSE). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid backup controlfile checkpoint |
| Long Text: | The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access. |
| Repair Text: | From Oracle doc: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | indeterminate controlfile checkpoint |
| Long Text: | The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access. |
| Repair Text: | From Oracle doc: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote archivelog destination must be a STANDBY database |
| Long Text: | The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances. |
| Repair Text: | From Oracle doc: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote archivelog destination database is opened for update |
| Long Text: | The database associated with the archive log destination service name is opened for update access. Remote archival of redo log files to standby databases opened for update access is not allowed. |
| Repair Text: | From Oracle doc: Shutdown the standby destination instance and re-open for read-only access or simple leave the standby instance mounted and unopened. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Archivelog Remote File Server process in Error state |
| Long Text: | The archive log remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data. |
| Repair Text: | From Oracle doc: Correct the problem at the standby database site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Archivelog standby database identifier mismatch |
| Long Text: | The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. |
| Repair Text: | From Oracle doc: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s sequence# %s does not need archiving |
| Long Text: | An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s sequence# %s not archived, no available destinations |
| Long Text: | An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors. |
| Repair Text: | From Oracle doc: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s sequence# %s not archived, media recovery disabled |
| Long Text: | An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed. |
| Repair Text: | From Oracle doc: Disable the standby destination or enable media recovery and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log for thread %s sequence# %s unavailable |
| Long Text: | The sustained standby database recovery operation has timed out waiting for the requested archived log file. |
| Repair Text: | From Oracle doc: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination |
| Long Text: | The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly. |
| Repair Text: | From Oracle doc: Set the primary archive destination to a valid non-NULL value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use %s with LOG_ARCHIVE_DEST_n |
| Long Text: | One of the following events caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1...5) parameter was encountered while fetching initialization parameters. An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. |
| Repair Text: | From Oracle doc: Eliminate any incompatible parameter definitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use %s with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST |
| Long Text: | One of the following events caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter was encountered while fetching initialization parameters. Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter. An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter. |
| Repair Text: | From Oracle doc: Eliminate any incompatible parameter definitions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST |
| Long Text: | With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value. |
| Repair Text: | From Oracle doc: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session %s destination cannot be the same as session %s destination |
| Long Text: | An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter. |
| Repair Text: | From Oracle doc: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL |
| Long Text: | An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL. |
| Repair Text: | From Oracle doc: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system %s destination cannot be the same as session %s destination |
| Long Text: | An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate. |
| Repair Text: | From Oracle doc: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s cannot be parsed |
| Long Text: | The value for the specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized option, or an option that is missing a required value. |
| Repair Text: | From Oracle doc: Correct the value for the LOG_ARCHIVE_DEST_n parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s contains repeated or conflicting options |
| Long Text: | The value for the specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter contained either repeated options or options that conflicted with each other. |
| Repair Text: | From Oracle doc: Correct the value for the LOG_ARCHIVE_DEST_n parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s contains an invalid reopen time |
| Long Text: | The value for the specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter contained a REOPEN option with an invalid numeric value. The valid range is 0-65535. |
| Repair Text: | From Oracle doc: Correct the value for the LOG_ARCHIVE_DEST_n parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s is missing a destination option |
| Long Text: | The value for the specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter failed to include a destination option. Valid destination options are LOCATION or SERVICE. |
| Repair Text: | From Oracle doc: Correct the value for the LOG_ARCHIVE_DEST_n parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | new %s causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires |
| Long Text: | With automatic archiving enabled, an attempt was made to change the specified LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...5) to a value that reduces the number of archive log destinations to less than the LOG_ARCHIVE_MIN_SUCCEED_DEST value. |
| Repair Text: | From Oracle doc: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations |
| Long Text: | An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations. |
| Repair Text: | From Oracle doc: Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1...5). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session specific change requires a LOG_ARCHIVE_DEST_n destination |
| Long Text: | The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command. |
| Repair Text: | From Oracle doc: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1...5) parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s destination %s exceeds %s character limit |
| Long Text: | The value for the specified parameter contained a destination string that is too long. |
| Repair Text: | From Oracle doc: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s destination %s cannot be translated |
| Long Text: | The value for the specified parameter contained a destination string that could not be translated. |
| Repair Text: | From Oracle doc: Use a valid destination string in the specified parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16033 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter %s destination cannot be the same as parameter %s destination |
| Long Text: | An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter. |
| Repair Text: | From Oracle doc: Specify a different value for one of the archive log parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16034 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | FROM parameter is incompatible with MANAGED recovery |
| Long Text: | Use of the FROM 'location' parameter is not allowed when MANAGED recovery has been specified. |
| Repair Text: | From Oracle doc: Correct the syntax and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16035 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | missing required keyword %s |
| Long Text: | The keywords STANDBY DATABASE are required when MANAGED recovery has been specified. |
| Repair Text: | From Oracle doc: Correct the syntax and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid MANAGED recovery CANCEL option |
| Long Text: | A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement. |
| Repair Text: | From Oracle doc: Specify either nothing or IMMEDIATE following CANCEL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user requested cancel of sustained recovery operation |
| Long Text: | The sustained standby database recovery operation has been canceled per user request. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log %s sequence# %s cannot be archived |
| Long Text: | An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error. |
| Repair Text: | From Oracle doc: No action is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RFS request version mismatch |
| Long Text: | A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site. |
| Repair Text: | From Oracle doc: Verify that compatible versions of Oracle are running on the primary and all standby sites. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby destination archivelog file is locked |
| Long Text: | The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process. |
| Repair Text: | From Oracle doc: Check for and eliminate duplicate standby destination archive log service names defined for the primary database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16041 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Remote File Server fatal error |
| Long Text: | The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible. |
| Repair Text: | From Oracle doc: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16042 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | user requested cancel immediate of sustained recovery operation |
| Long Text: | The sustained standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16055 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | FAL request rejected |
| Long Text: | FAL server rejects the FAL request from the FAL client. This may be caused by different reasons. |
| Repair Text: | From Oracle doc: to solve the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16058 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby database instance is not mounted |
| Long Text: | The RFS process on the standby database received an internal error. |
| Repair Text: | From Oracle doc: Check the standby alert log and RFS trace files for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16401 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | archivelog rejected by RFS |
| Long Text: | An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database. |
| Repair Text: | From Oracle doc: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-16922 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the password for %d user(s) is already expired. For user: %s in databsae %s. |
| Long Text: | The user's account password has expired and the password needs to be changed. |
| Repair Text: | From Oracle doc: Change the password or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid outline name |
| Long Text: | The parser detected a missing or invalid outline name. |
| Repair Text: | From Oracle doc: Re-issue the command, specifying a valid outline name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no options specified for ALTER OUTLINE |
| Long Text: | The parser detected that no clause was specified on the command. |
| Repair Text: | From Oracle doc: Re-issue the command, specifying a valid ALTER OUTLINE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified outline does not exist |
| Long Text: | Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream. |
| Repair Text: | From Oracle doc: Check for the existence of the outline and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an outline already exists with this signature |
| Long Text: | The signature generation algorithm generates signatures that are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case. |
| Repair Text: | From Oracle doc: Either re-issue the statement that led to the outline being created with some white space added or force the outline to be created in a different category. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | outline already exists |
| Long Text: | An outline already exists, either with the specified name, or for the specified SQL text. |
| Repair Text: | From Oracle doc: Try again with another name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | create any outline privilege is required for this operation |
| Long Text: | Create any outline privilege is required for the attempted operation. |
| Repair Text: | From Oracle doc: Make sure you have create any outline privilege and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | drop any outline privilege is required for this operation |
| Long Text: | Drop any outline privilege is required for the attempted operation. |
| Repair Text: | From Oracle doc: Make sure you have drop any outline privilege and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | alter any outline privilege is required for this operation |
| Long Text: | Alter any outline privilege is required for the attempted operation. |
| Repair Text: | From Oracle doc: Make sure you have alter any outline privilege and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot find OUTLN schema |
| Long Text: | The database creation script that creates this schema must not have been executed. |
| Repair Text: | From Oracle doc: Review the log files to see what happened when the database was created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | one or more outline system tables do not exist |
| Long Text: | Either the database creation script that creates these tables was not executed or a user accidently deleted the table. |
| Repair Text: | From Oracle doc: Review the log files to see what happened when the database was created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-18010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | command missing mandatory CATEGORY keyword |
| Long Text: | User failed to specify the CATEGORY keyword. |
| Repair Text: | From Oracle doc: Re-issue the command with the CATEGORY keyword included. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | System type conflict with object SYS.%s |
| Long Text: | The user had an object with the same name as one of the system types. The system types were not initialized properly. |
| Repair Text: | From Oracle doc: Remove the conflicting object and re-run migration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device block size %s is invalid |
| Long Text: | The device block size returned by sequential I/O OSD is invalid. |
| Repair Text: | From Oracle doc: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | read error on file "%s", blockno %s (blocksize=%s) |
| Long Text: | Read error on input file. |
| Repair Text: | From Oracle doc: Check the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | write error on file "%s", blockno %s (blocksize=%s) |
| Long Text: | Write error on output file. |
| Repair Text: | From Oracle doc: Check the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot obtain information on device, name="%s", type="%s", parms="%s" |
| Long Text: | Call to get device information returned an error. |
| Repair Text: | From Oracle doc: Check device name, type, and parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to create file "%s" |
| Long Text: | Call to create file returned an error. |
| Repair Text: | From Oracle doc: Check additional messages and check access permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to identify file "%s" |
| Long Text: | Call to identify the file returned an error. |
| Repair Text: | From Oracle doc: Check additional messages, and check whether the file exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to create sequential file, name="%s", parms="%s" |
| Long Text: | Call to create the sequential file returned an error. |
| Repair Text: | From Oracle doc: Check additional messages, check access permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to retrieve sequential file, handle="%s", parms="%s" |
| Long Text: | Call to retrieve the sequential file returned an error. |
| Repair Text: | From Oracle doc: Check additional messages, and check if the file exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to delete file "%s" |
| Long Text: | Call to delete the file returned an error. |
| Repair Text: | From Oracle doc: Check additional messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to delete sequential file, handle="%s", parms="%s" |
| Long Text: | Call to delete the sequential file returned an error. |
| Repair Text: | From Oracle doc: Check additional messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to set size of %s blocks for file "%s" (blocksize=%s) |
| Long Text: | Call to resize the file returned an error. |
| Repair Text: | From Oracle doc: Check additional messages. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager. |
| Repair Text: | From Oracle doc: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19550 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use backup/restore functions while using dispatcher |
| Long Text: | An attempt was made to use backup/restore functions while connected to the dispatcher in a multi-threaded server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process. |
| Repair Text: | From Oracle doc: Connect directly to the instance then re-execute the backup or restore function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device is busy, device type: %s, device name: %s |
| Long Text: | The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy. |
| Repair Text: | From Oracle doc: Either attempt to allocate another device or wait until the required device is no longer busy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device type %s is invalid |
| Long Text: | The device type indicated is invalid. |
| Repair Text: | From Oracle doc: Supply a correct device type and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19553 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device name %s is invalid |
| Long Text: | The device name indicated is invalid. |
| Repair Text: | From Oracle doc: Supply a correct device name and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19554 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error allocating device, device type: %s, device name: %s |
| Long Text: | The specified device could not be allocated. |
| Repair Text: | From Oracle doc: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19555 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value |
| Long Text: | The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range. |
| Repair Text: | From Oracle doc: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19556 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred |
| Long Text: | The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination. |
| Repair Text: | From Oracle doc: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19557 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device error, device type: %s, device name: %s |
| Long Text: | An error occurred in the platform-specific device code. |
| Repair Text: | From Oracle doc: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19558 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error de-allocating device |
| Long Text: | The specified device could not be de-allocated. |
| Repair Text: | From Oracle doc: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19559 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error sending device command: %s |
| Long Text: | An error occurred while sending the indicated command to the session device. |
| Repair Text: | From Oracle doc: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19560 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is not a valid device limit |
| Long Text: | An invalid type of device limit was specified in a call to X$DBMS_BACKUP_RESTORE.SETLIMIT. |
| Repair Text: | From Oracle doc: Use one of the documented limits: KBYTES, READRATE, or PARALLEL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19561 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s requires a DISK channel |
| Long Text: | The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found. |
| Repair Text: | From Oracle doc: Deallocate the current device and allocate a DISK channel, then retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19562 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is empty |
| Long Text: | The indicated file, which is an archive log, control file, or datafile was found to be empty during a copy, backup, or scan] operation. |
| Repair Text: | From Oracle doc: Ensure that the correct files are being specified for the copy or backup operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19563 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s header validation failed for file %s |
| Long Text: | When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, the header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file), belonging to the current database. |
| Repair Text: | From Oracle doc: Ensure that the correct files are being specified for the copy or backup operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19564 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred writing %s bytes at block number %s |
| Long Text: | An error occurred while writing to a file. |
| Repair Text: | From Oracle doc: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19565 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices |
| Long Text: | An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled. |
| Repair Text: | From Oracle doc: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19566 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | exceeded limit of %s corrupt blocks for file %s |
| Long Text: | The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup. |
| Repair Text: | From Oracle doc: No action required. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19567 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot shrink file %s because it is being backed up or copied |
| Long Text: | An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied. |
| Repair Text: | From Oracle doc: Retry the resize after the backup or copy is complete. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19568 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a device is already allocated to this session |
| Long Text: | A device cannot be allocated to a session if another device is already allocated. |
| Repair Text: | From Oracle doc: Deallocate the current device. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19569 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no device is allocated to this session |
| Long Text: | An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated. |
| Repair Text: | From Oracle doc: Allocate a device then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19570 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file number %s is outside valid range of 1 through %s |
| Long Text: | A file number used in a copy, backup, or restore operation is not valid for the current database. |
| Repair Text: | From Oracle doc: Specify a valid file number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19571 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s recid %s stamp %s not found in controlfile |
| Long Text: | The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file. |
| Repair Text: | From Oracle doc: Specify a correct RECID/stamp and retry the copy or backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19572 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot process file %s, file is being being resized |
| Long Text: | The input file specified for a copy or backup operation could not be opened because the file is being resized. |
| Repair Text: | From Oracle doc: Wait for the resize to complete then retry the copy or backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19573 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot obtain %s enqueue for datafile %s |
| Long Text: | The file access enqueue could not be obtained for a file specified in a backup, copy or restore operation. If the enqueue type shown is SHARED, then the file is the input file for a backup or copy. If the type is EXCLUSIVE, then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file. In this case, the file must be offline or the database must be closed. If the type is read-only, then you are attempting to back up or copy this file while the database is in NOARCHIVELOG mode. |
| Repair Text: | From Oracle doc: Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19574 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | output filename must be specified |
| Long Text: | This type of copy or restore requires an output file name. |
| Repair Text: | From Oracle doc: Specify an output file name and retry the copy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19575 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | expected %s blocks in file %s, found %s |
| Long Text: | During a backup, restore, copy, or scan operation, the indicated file did not contain as many blocks as were indicated in the file header. |
| Repair Text: | From Oracle doc: The input copy or backup piece is probably corrupt. If another backup or copy exists of the file that is being restored, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19576 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s not defined in control file |
| Long Text: | The specified file number was not found in the control file. |
| Repair Text: | From Oracle doc: Specify a correct file number and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19577 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is MISSING |
| Long Text: | A copyDataFileCopy, restoreDataFileTo or proxyRestoreDataFile function specified a file number but no output file name, indicating that the output file name should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the control file cannot be used for restoration. |
| Repair Text: | From Oracle doc: Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19578 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | end of volume while duplexing to sequential files, backup piece incomplete |
| Long Text: | An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently. |
| Repair Text: | From Oracle doc: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19580 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s conversation not active |
| Long Text: | A backup or restore operation was attempted before a conversation was started. |
| Repair Text: | From Oracle doc: Start a conversation then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19581 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no files have been named |
| Long Text: | An attempt was made to proceed from the file naming phase to the piece processing phase of a backup or restore conversation before any files have been specified for backup or restore. |
| Repair Text: | From Oracle doc: Specify some files then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19583 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | conversation terminated due to error |
| Long Text: | An error occurred which forced the termination of the current backup or restore conversation. |
| Repair Text: | From Oracle doc: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19584 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s already in use |
| Long Text: | The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database. |
| Repair Text: | From Oracle doc: Specify a different name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19585 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | premature end of volume on piece %s |
| Long Text: | While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set. |
| Repair Text: | From Oracle doc: Retry the piece with a larger piece of output media. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19586 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s k-byte limit is too small to hold piece directory |
| Long Text: | The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data. |
| Repair Text: | From Oracle doc: Use the setLimit procedure to increase the k-byte limit and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19587 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred reading %s bytes at block number %s |
| Long Text: | An error occurred while reading from a file. |
| Repair Text: | From Oracle doc: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19588 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s recid %s stamp %s is no longer valid |
| Long Text: | The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was 'consumed' by a switchToCopy operation. |
| Repair Text: | From Oracle doc: If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new RECID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19589 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is not a snapshot or backup controlfile |
| Long Text: | The control file that is the source for a backup or copy operation is not a snapshot or backup control file. |
| Repair Text: | From Oracle doc: Specify the name of a snapshot or backup control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19590 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | conversation already active |
| Long Text: | An attempt was made to begin a backup or restore conversation, but another conversation is already active in this session. |
| Repair Text: | From Oracle doc: Either continue the current conversation, or call backupCancel or restoreCancel to end the current conversation before starting a new one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19592 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | wrong %s conversation type |
| Long Text: | An attempt was made to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation. |
| Repair Text: | From Oracle doc: No action required. The conversation is still active, and more files can be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19593 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | datafile number %s already included as %s |
| Long Text: | This datafile is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of a datafile. |
| Repair Text: | From Oracle doc: No action required. The conversation is still active, and more files can be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19594 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | controlfile already included as %s |
| Long Text: | The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file. |
| Repair Text: | From Oracle doc: No action required. The conversation is still active, and more files can be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19595 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | archivelog thread %s sequence %s already included as %s |
| Long Text: | The indicated archive log has already been specified for inclusion in this backup conversation. A backup conversation may process only one copy of any archive log. |
| Repair Text: | From Oracle doc: No action required. The conversation is still active, and more files can be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19596 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot controlfile has not been created |
| Long Text: | You requested that the snapshot control file be included in the backup set, but no snapshot control file has been created for this instance. |
| Repair Text: | From Oracle doc: Specify a different control file name, or call cfileMakeAndUseSnapshot to create the snapshot control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19597 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s blocksize %s does not match set blocksize of %s |
| Long Text: | A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size. |
| Repair Text: | From Oracle doc: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19598 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | starting SCN must be specified for incremental backup |
| Long Text: | No starting SCN was specified to backupDataFile or backupDataFileCopy, but the current backup conversation is for an incremental backup, which requires that a non-zero SCN be specified for all datafiles. |
| Repair Text: | From Oracle doc: The conversation is still active. Respecify the datafile with a non-zero SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19599 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | block number %s is corrupt in %s %s |
| Long Text: | A corrupt block was found in a control file, archive log, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archive logs, or backup pieces. |
| Repair Text: | From Oracle doc: No action required. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input file is %s %s (%s) |
| Long Text: | This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown. For a datafile, the file number refers to the datafile's absolute file number as shown in the DBA_DATA_FILES view. For a datafile-copy, the file number refers to the copy's control file record number as shown in the V$DATAFILE_COPY view. For a datafile-copy, the file number refers to the copy's control file record number as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log, the file number refers to the log's control file record number as shown in the RECID column of the V$ARCHIVED_LOG view. |
| Repair Text: | From Oracle doc: Other messages should display to help pinpoint the cause and the solution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | output file is %s %s (%s) |
| Long Text: | This message identifies the output file for a failed copy operation. The fields are as described in message 19600. When creating a new datafile copy, its control file record number may not have been determined when the message is printed. In that case, the record number shown is zero. |
| Repair Text: | From Oracle doc: See other error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19602 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot backup or copy active file in NOARCHIVELOG mode |
| Long Text: | An attempt was made to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs. |
| Repair Text: | From Oracle doc: Take the tablespace offline clean or close the database and retry the copy or backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19604 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | conversation file naming phase is over |
| Long Text: | A call was made to specify a file to be backed up or restored after the first backup piece has been processed. |
| Repair Text: | From Oracle doc: You cannot specify more files to be processed during a backup or restore conversation after the first backup piece has been processed. If more files must be specified, you must begin a new conversation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19605 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input filename must be specified |
| Long Text: | The input file name was not specified for a control file copy operation. |
| Repair Text: | From Oracle doc: Specify an input file name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot copy or restore to snapshot controlfile |
| Long Text: | A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file. |
| Repair Text: | From Oracle doc: Specify a different file name and retry the operation. If this is a restore, then the restore conversation remains active and more files may be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19607 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is an active controlfile |
| Long Text: | A control file copy, restore, or backup specified the name of a control file named in the INIT.ORA file as the input or output file. |
| Repair Text: | From Oracle doc: Specify a different file name and retry the operation. If this is a backup or restore conversation, then the conversation remains active and more files may be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19608 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is not a backup piece |
| Long Text: | The specified file is not a backup piece produced by the DBMS_BACKUP_RESTORE package. Either the first block of the backup piece is corrupt or this file is not a backup piece. |
| Repair Text: | From Oracle doc: Specify a different file name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19609 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is from different backup set: stamp %s count %s |
| Long Text: | The specified file is not from the backup set which is currently being processed. It is part of a different backup set. The identification of the set containing this piece is shown. |
| Repair Text: | From Oracle doc: Specify the correct backup piece and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19610 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | directory block %s is corrupt |
| Long Text: | The indicated directory block failed checksum validation. This backup piece is unusable. |
| Repair Text: | From Oracle doc: Supply another copy of the same backup piece, or terminate the restore conversation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19611 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | backup piece out of order. Expected %s but found %s |
| Long Text: | This backup piece is out of sequence. |
| Repair Text: | From Oracle doc: Supply the correct backup piece. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19612 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s not restored due to %s |
| Long Text: | The indicated file could not be restored, because all of its data blocks were not found in the backup piece. |
| Repair Text: | From Oracle doc: The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by reprocessing the current piece, then the restore conversation must be cancelled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19613 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s not found in backup set |
| Long Text: | The indicated file could not be restored, because it is not in this backup set. If the file number is zero, then this refers to the control file. |
| Repair Text: | From Oracle doc: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19614 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archivelog thread %s sequence %s not found in backup set |
| Long Text: | The indicated archived log file was named explicitly for restoration but is not contained in this backup set. |
| Repair Text: | From Oracle doc: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19615 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | some files not found in backup set |
| Long Text: | Some files that were specified for restoration were not found in the backup set directory. Message 19613 or 19614 is issued for each file that was not found. |
| Repair Text: | From Oracle doc: See the instructions for message 19613. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19616 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | output filename must be specified if database not mounted |
| Long Text: | A datafile restore specified no target file name, but the database is not mounted. The database must be mounted when no target file name is specified, so that the target file name can be obtained from the control file. |
| Repair Text: | From Oracle doc: The restore conversation remains active. If you wish to restore datafiles without their target file names, then mount the database before continuing. Otherwise, a target file name must be specified on all datafile restoration calls. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19617 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s contains different resetlogs data |
| Long Text: | The indicated file contains resetlogs data which is different from the archived log files which are already included in the backup set. All archived log files in a backup set must have the same resetlogs data. |
| Repair Text: | From Oracle doc: The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19618 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot name files after restoreValidate has been called |
| Long Text: | A call was made to specify a file to restore from a backup set, but a previous call to restoreValidate has already been made. |
| Repair Text: | From Oracle doc: You must cancel and restart the conversation if you wish to specify files to restore. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19619 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot call restoreValidate after files have been named |
| Long Text: | restoreValidate was called after some files had already been specified for restoration. |
| Repair Text: | From Oracle doc: You must cancel and restart the conversation if you wish to call restoreValidate. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19621 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archivelog range has already been specified |
| Long Text: | A range of logs has already been specified. Only one SCN range may be specified per conversation. |
| Repair Text: | From Oracle doc: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19622 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archivelog thread %s sequence %s not restored due to %s |
| Long Text: | The indicated file could not be restored, because all of its data blocks were not found in the backup piece. |
| Repair Text: | From Oracle doc: The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by reprocessing the current piece, then the restore conversation must be cancelled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19623 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is open |
| Long Text: | A SwitchToCopy operation specified a datafile copy whose parent datafile is open. |
| Repair Text: | From Oracle doc: Take the owning tablespace offline or close the database, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19624 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation failed, retry possible |
| Long Text: | A backup, restore or image copy operation failed with an I/O error. If the source of the I/O error can be corrected, then the operation may be retried. |
| Repair Text: | From Oracle doc: This message is used by Recovery Manager to decide whether or not to retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19625 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error identifying file %s |
| Long Text: | A file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. An operating system-specific error accompanies this error to help pinpoint the problem. |
| Repair Text: | From Oracle doc: Specify an different file and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19626 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | backup set type is %s - can not be processed by this conversation |
| Long Text: | The data in the backup set is not compatible with the current conversation. |
| Repair Text: | From Oracle doc: Either supply the first piece from a backup set that matches the current conversation or start a new restore conversation which can process this backup set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19627 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot read backup pieces during controlfile application |
| Long Text: | This is a control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation. |
| Repair Text: | From Oracle doc: The conversation is still active and more control files may be applied. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19628 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SCN range |
| Long Text: | The starting SCN for restoreRedoLogRange is greater than the ending SCN. |
| Repair Text: | From Oracle doc: Specify a starting SCN which is less than or equal to the ending SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19629 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no files in specified archivelog SCN range |
| Long Text: | This backup set contains no files in the specified range. |
| Repair Text: | From Oracle doc: Either supply a backup set that contains files in the correct range or start a new conversation and specify a range which will select some files from this backup set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19630 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | end of volume encountered while copying backup piece |
| Long Text: | While copying a backup piece from the operating system native file system to an output device, the output device encountered end-of-volume. |
| Repair Text: | From Oracle doc: The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19631 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archivelog record contains no file name |
| Long Text: | This archive log record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost. |
| Repair Text: | From Oracle doc: Specify the RECID of an archive log record that contains a file name. Fixed view V$ARCHIVED_LOG can be used to examine the archived logs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19632 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file name not found in controlfile |
| Long Text: | The name passed to getFno was not found in the control file. |
| Repair Text: | From Oracle doc: Supply a valid file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19633 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | controlfile record %s is out of sync with recovery catalog |
| Long Text: | The control file record describing the file to be deleted in a call to deleteBackupPiece, deleteDataFilecopy, proxyDelete or deleteArchivedLog does not match the validation data supplied by Recovery Manager. |
| Repair Text: | From Oracle doc: contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19634 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | filename required for this function |
| Long Text: | The FNAME or handle parameter was not specified for deletePiece, deleteDataFileCopy, deleteRedoLog or proxyDelete. |
| Repair Text: | From Oracle doc: Specify the FNAME or handle parameter when calling these functions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19635 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input and output filenames are identical |
| Long Text: | Identical input and output file names were specified for a datafile copy operation. |
| Repair Text: | From Oracle doc: Specify an output file name which is different from the input file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19636 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | archivelog thread %s sequence %s already included |
| Long Text: | The indicated archive log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archive log. |
| Repair Text: | From Oracle doc: No action required. The conversation is still active, and more files can be specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19637 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | backupPieceCreate requires file name when using DISK device |
| Long Text: | The session device is currently allocated to disk, and so a file name is required. |
| Repair Text: | From Oracle doc: Supply a file name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19638 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is not current enough to apply this incremental backup |
| Long Text: | The checkpoint of the target for this incremental backup is less than the start of the incremental backup. If this backup were applied, then any changes made between the datafile checkpoint and the start of the incremental backup could be lost. |
| Repair Text: | From Oracle doc: Supply a backup set that can be applied and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19639 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is more current than this incremental backup |
| Long Text: | The checkpoint of the target for this incremental backup is greater than or equal to the checkpoint of the file in the incremental backup set. This backup cannot advance the checkpoint of the target file, so there is no point in applying it. |
| Repair Text: | From Oracle doc: Supply a backup set that can be applied and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19640 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile checkpoint is SCN %s time %s |
| Long Text: | This message identifies the datafile checkpoint for a datafile that was too old to take an incremental backup from, or the target of an incremental restore that could not be applied. |
| Repair Text: | From Oracle doc: See other error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19641 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | backup datafile checkpoint is SCN %s time %s |
| Long Text: | This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied. |
| Repair Text: | From Oracle doc: See other error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19642 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incremental-start SCN is %s |
| Long Text: | This message identifies the starting SCN of an incremental backup that could not be applied. |
| Repair Text: | From Oracle doc: See other error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19643 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s: incremental-start SCN is too recent |
| Long Text: | The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed. |
| Repair Text: | From Oracle doc: Specify a smaller incremental-start SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19644 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s: incremental-start SCN is prior to resetlogs SCN %s |
| Long Text: | The incremental-start SCN which was specified when starting an incremental datafile backup is less than the resetlogs SCN. |
| Repair Text: | From Oracle doc: Specify a larger incremental-start SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19645 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s: incremental-start SCN is prior to creation SCN %s |
| Long Text: | The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile's creation SCN. |
| Repair Text: | From Oracle doc: Specify a larger incremental-start SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19646 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change size of datafile %s from %s to %s |
| Long Text: | The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size. |
| Repair Text: | From Oracle doc: Examine the other messages which should be present to indicate the cause of the failure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19647 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-zero LEVEL cannot be specified when INCREMENTAL is FALSE |
| Long Text: | BackupSetDataFile was called with a non-zero BACKUP_LEVEL and a FALSE incremental indication. |
| Repair Text: | From Oracle doc: Either set incremental to TRUE or change BACKUP_LEVEL to zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19648 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s: incremental-start SCN equals checkpoint SCN |
| Long Text: | The incremental-start SCN which was specified when starting an incremental datafile backup is equal to the datafile's checkpoint SCN. Since an incremental backup can only be applied to a datafile whose checkpoint SCN is between the backup set incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no datafile that this backup set could ever be applied to. |
| Repair Text: | From Oracle doc: Specify a smaller incremental-start SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19649 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | offline-range record recid %s stamp %s not found in file %s |
| Long Text: | applyOfflineRange was called with a RECID/stamp which was not found in the indicated control file. This probably means that the specified control file is no longer the same control file that Recovery Manager thinks it is. |
| Repair Text: | From Oracle doc: Specify the RECID/stamp of a record that exists in the control file copy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19650 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Offline-range record recid %s stamp %s in file %s has SCN %s |
| Long Text: | This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file. |
| Repair Text: | From Oracle doc: See other error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19651 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot apply offline-range record to datafile %s: SCN mismatch |
| Long Text: | applyOfflineRange cannot apply an offline-range record to a target datafile unless the datafile's checkpoint SCN exactly matches the offline-clean SCN in the specified offline-range record. |
| Repair Text: | From Oracle doc: Specify an offline-range record whose offline-clean SCN matches the target datafile's checkpoint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19652 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot apply offline-range record to datafile %s: file is fuzzy |
| Long Text: | The target datafile for an applyOfflineRange call is fuzzy. |
| Repair Text: | From Oracle doc: Specify a target datafile that is closed cleanly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19653 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot switch to older file incarnation |
| Long Text: | SwitchToCopy was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up. |
| Repair Text: | From Oracle doc: Restore and mount an earlier control file. It is acceptable to use a control file that was backed up prior to the creation of the specified datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19654 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must use backup controlfile to switch file incarnations |
| Long Text: | This switchToCopy operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file. |
| Repair Text: | From Oracle doc: Restore and mount a backup control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19655 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot switch to incarnation with different resetlogs data |
| Long Text: | This switchToCopy operation is attempting to switch to a datafile which comes from a different resetlogs version of the database. |
| Repair Text: | From Oracle doc: Either restore a backup control file that was taken from the same database version as the target datafile-copy, or switch to a different datafile-copy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19656 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot backup, copy, or delete online log %s |
| Long Text: | The indicated log file is an active log. You can only backup, copy, or delete archived logs. |
| Repair Text: | From Oracle doc: The indicated log file cannot be processed. Select another file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19657 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot inspect current datafile %s |
| Long Text: | The file being inspected is already part of the currently mounted database. |
| Repair Text: | From Oracle doc: No action required. The file is already part of the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19658 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot inspect %s - file is from different resetlogs |
| Long Text: | The resetlogs data in the log file being inspected does not match that in the currently mounted control file. |
| Repair Text: | From Oracle doc: The indicated file cannot be processed; inspect another file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19659 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incremental restore would advance file %s past resetlogs |
| Long Text: | This incremental backup cannot be applied to the specified datafile, because the datafile is from an earlier incarnation of the database, and its checkpoint would be advanced too far to be recoverable in the current incarnation of the database. |
| Repair Text: | From Oracle doc: This incremental cannot be applied to this datafile. If you wish to recover the file to the resetlogs SCN so that the database can be opened with the RESETLOGS option, then you must use redo-log recovery, not incremental restore, to continue recovering this file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19660 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | some files in the backup set could not be verified |
| Long Text: | A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set. |
| Repair Text: | From Oracle doc: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19661 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s could not be verified |
| Long Text: | Some data blocks for the indicated datafile were corrupt in the backup set. |
| Repair Text: | From Oracle doc: Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19662 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | archived log thread %s sequence %s could not be verified |
| Long Text: | Some data blocks for the indicated archived log were corrupt in the backup set. |
| Repair Text: | From Oracle doc: Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19663 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot apply current offline range to datafile %s |
| Long Text: | An attempt was made to apply the current offline range to the specified datafile, but the datafile is either not current enough or is not at the correct SCN to apply the offline range. |
| Repair Text: | From Oracle doc: The datafile remains unchanged. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19664 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | file type: %s, file name: %s |
| Long Text: | This message is issued to identify the file which is the subject of an error. |
| Repair Text: | From Oracle doc: No action required. This is an informational message. There should be other Oracle messages explaining the cause of the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19665 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | size %s in file header does not match actual file size of %s |
| Long Text: | The size of the file as indicated in the file header does not match the true size of the file. The two differing sizes are shown in units of logical blocks. |
| Repair Text: | From Oracle doc: This file is not usable; it has most likely been truncated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19666 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot do incremental restore of the controlfile |
| Long Text: | The control file was included in an incremental restore conversation |
| Repair Text: | From Oracle doc: If you wish to restore the control file, you must do a full restore of the control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19667 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot do incremental restore of datafile %s |
| Long Text: | The backup of the datafile is a full backup. |
| Repair Text: | From Oracle doc: If you wish to restore the datafile, you must do a full restore of the datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19668 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot do full restore of datafile %s |
| Long Text: | The backup of the datafile is an incremental backup. |
| Repair Text: | From Oracle doc: If you wish to restore the datafile, you must do an incremental restore of the datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19669 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | proxy copy functions cannot be run on DISK channel |
| Long Text: | A proxy copy procedure was called, but the device which is allocated to the current session has type DISK. |
| Repair Text: | From Oracle doc: Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a third-party media management software product that supports the this backup/restore feature. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19670 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s already being restored |
| Long Text: | A proxy restore function has already named this file as a restore destination. |
| Repair Text: | From Oracle doc: Use a different file name. If this message occurs during a Recovery Manager job, then this is an internal error in Recovery Manager, and you should contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19671 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | media management software returned invalid proxy handle |
| Long Text: | During a proxy backup or restore, the media management software returned an invalid file handle. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. |
| Repair Text: | From Oracle doc: Contact the media management software vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19672 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | media management software returned invalid file status |
| Long Text: | During a proxy backup or restore, the media management software returned an invalid file status. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. |
| Repair Text: | From Oracle doc: Contact the media management software vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19673 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error during proxy copy of file %s |
| Long Text: | During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully. |
| Repair Text: | From Oracle doc: There should be other errors on the error stack which explain why the file could not be successfully copied. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19674 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | file %s is already being backed up with proxy copy |
| Long Text: | Recovery Manager attempted to back up the specified file with proxy copy, but the file is already being backed up by another Recovery Manager job. |
| Repair Text: | From Oracle doc: Wait until the other Recovery Manager backup of this file is complete, then retry the backup. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19675 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s was modified during proxy copy |
| Long Text: | A proxy backup of the specified file failed because the file was brought online or otherwise modified while the proxy backup was in progress. This file was offline or read only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress. |
| Repair Text: | From Oracle doc: Take another backup of this file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19676 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | one or more files failed during proxy backup or restore |
| Long Text: | During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully. |
| Repair Text: | From Oracle doc: Examine the messages regarding the specific files to determine the cause of the problems. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19700 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device type exceeds maximum length of %s |
| Long Text: | The device type indicated is invalid. |
| Repair Text: | From Oracle doc: Supply a correct device type and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device name exceeds maximum length of %s |
| Long Text: | The device name indicated is invalid. |
| Repair Text: | From Oracle doc: Supply a correct device name and retry the allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device parameter exceeds maximum length of %s |
| Long Text: | The device parameter exceeds the port-specific maximum length. |
| Repair Text: | From Oracle doc: Correct the parameter and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | device command %s exceeds maximum length of %s |
| Long Text: | The device command string exceeds maximum length. |
| Repair Text: | From Oracle doc: Correct the command and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file name exceeds maximum length of %s |
| Long Text: | The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system. |
| Repair Text: | From Oracle doc: Retry the operation with a shorter file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tag value exceeds maximum length of %s characters |
| Long Text: | During a backup or copy operation, the user supplied a tag value too long to fit in the file header. |
| Repair Text: | From Oracle doc: Supply a shorter tag and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SCN |
| Long Text: | The input SCN is either not a positive integer or too large. |
| Repair Text: | From Oracle doc: Check the input SCN and make sure it is a valid SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19707 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid record block number - %s |
| Long Text: | The input number is either negative or too large. |
| Repair Text: | From Oracle doc: Check the input record block number and make sure it is a valid number clauses in the CREATE DATABASE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | log destination exceeds maximum length of %s characters |
| Long Text: | When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum. |
| Repair Text: | From Oracle doc: Supply a shorter destination and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | numeric parameter must be non-negative integer |
| Long Text: | A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion. |
| Repair Text: | From Oracle doc: Supply a valid numeric parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19720 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Error occurred when converting an OCI number into an SCN |
| Long Text: | This is most likely caused by an invalid SCN number that came from an external file, such as an export file. |
| Repair Text: | From Oracle doc: See other errors on the error stack to look for the source of the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19721 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot find datafile with absolute file number %s in tablespace %s |
| Long Text: | Cannot find one of the data files that should be in the pluggable set. |
| Repair Text: | From Oracle doc: Make sure all datafiles are specified via import command line option or parameter files. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19722 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s is an incorrect version |
| Long Text: | The datafile is an incorrect version. It contains either less or more changes then the desired version. |
| Repair Text: | From Oracle doc: Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19723 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot recreate plugged in read-only datafile %s |
| Long Text: | The datafile is plugged in read only. It cannot re-created. |
| Repair Text: | From Oracle doc: Use ALTER DATABASE RENAME FILE command instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19724 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot too old: snapshot time is before file %s plug-in time |
| Long Text: | The snapshot SCN is before the SCN at which the referred datafile is plugged into the database. |
| Repair Text: | From Oracle doc: retry the query. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19725 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not acquire plug-in enqueue |
| Long Text: | There maybe another ALTER DATABASE RESET COMPATIBILITY command issued concurrently, preventing this process from acquiring the plug-in enqueue. |
| Repair Text: | From Oracle doc: Retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19726 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot plug data [%s] at level %s into database running at compatibility level %s |
| Long Text: | Some of the data in the pluggable set requires a compatibility level higher than what is currently allowed by the database. The string in square bracket is the name of the compatibility type associated with the data. |
| Repair Text: | From Oracle doc: Raise the value of the COMPATIBLE initialization parameter and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19727 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot plug data [%s] at level %s into database running Oracle %s |
| Long Text: | Some of the data in the pluggable set requires a compatibility level higher than the release level of the Oracle executable. The string in square bracket is the name of the compatibility type associated with the data. |
| Repair Text: | From Oracle doc: Upgrade Oracle and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19728 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data object number conflict between table %s and partition %s in table %s |
| Long Text: | The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One cannot exchange the table with the partition in this case. |
| Repair Text: | From Oracle doc: Use the ALTER TABLE MOVE PARTITION command to move the offending partition, so that the partition will get a new data object number. Retry the operation then. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19729 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File %s is not the initial version of the plugged in datafile |
| Long Text: | The file is not the initial version of the plugged in datafile. |
| Repair Text: | From Oracle doc: Use the correct initial version of the plugged in datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19730 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not convert offline plugged-in datafile %s |
| Long Text: | As part of making a tablespace read-write, we need to convert datafiles that are plugged in read only. The file must be online. |
| Repair Text: | From Oracle doc: Bring the datafile online and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19731 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot apply change to unverified plugged-in datafile %s |
| Long Text: | Recovery was not able to verify the referred datafile according to information in the control file. Before encountering this change vector for this file, somehow recovery did not encounter the file conversion redo that is supposed to verify the file. This may happen due to corrupted or incorrect control file used for media recovery. |
| Repair Text: | From Oracle doc: Use the correct control file and continue recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19732 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect number of datafiles for tablespace %s |
| Long Text: | The number of datafiles in the export file for the referred tablespace is not the same as expected. This is most likely caused by a user editing the export file. |
| Repair Text: | From Oracle doc: Use the correct export file and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19733 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | COMPATIBLE parameter needs to be %s or greater |
| Long Text: | The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter. |
| Repair Text: | From Oracle doc: Shutdown and restart with a higher compatibility setting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19734 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong creation SCN - control file expects converted plugged-in datafile |
| Long Text: | When a tablespace is plugged into a database, the tablespace is initially read only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the initial version of plugged-in datafile. |
| Repair Text: | From Oracle doc: Either restore the converted datafile or continue recovering the datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19735 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong creation SCN - control file expects initial plugged-in datafile |
| Long Text: | When a tablespace is plugged into a database, the tablespace is initially read only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the converted datafile. |
| Repair Text: | From Oracle doc: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19736 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not plug a tablespace into a database using a different national character set |
| Long Text: | Oracle does not support plugging a tablespace into a database using a different national character set. |
| Repair Text: | From Oracle doc: Use import/export or unload/load to move data instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19815 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | WARNING: %s of %s bytes is %s used, and has %s remaining bytes available |
| Long Text: | DB_RECOVERY_FILE_DEST is running out of disk space. |
| Repair Text: | From Oracle doc: Action: One of the following: 1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 2. Backup files to tertiary device using RMAN. 3. Consider changing RMAN retention policy. 4. Consider changing RMAN archivelog deletion policy. 5. Delete files from recovery area using RMAN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-19999 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skip_row procedure was called |
| Long Text: | The SKIP_ROW procedure was called which raises this error. |
| Repair Text: | From Oracle doc: SKIP_ROW should only be called within a trigger or a procedure called by a trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-20000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | The stored procedure RAISE_APPLICATION_ERROR was called which causes this error to be generated. |
| Repair Text: | From Oracle doc: Correct the problem as described in the error message or contact the application administrator or database administrator for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error number argument to raise_application_error of string%s is out of range |
| Long Text: | An attempt was made to specify a number not in the allowed range. |
| Repair Text: | From Oracle doc: Use an error number in the range of -20000 to -20999, inclusive. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error number argument to raise_system_error of string%s is out of range |
| Long Text: | An attempt was made to specify a number not in the allowed range. |
| Repair Text: | From Oracle doc: Use an error number in the range of -23300 to -24299, or -29300 to -29399, inclusive. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | objects option not installed |
| Long Text: | The objects option is not installed at this site. object types and other object features are, therefore, unavailable. |
| Repair Text: | From Oracle doc: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact Oracle Customer Support if the objects option needs to be purchased. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not initialized in object mode |
| Long Text: | This function requires the OCI process to be initialized in object mode. |
| Repair Text: | From Oracle doc: Specify OCI_OBJECT mode when calling OCIInitialize(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s] |
| Long Text: | This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition. |
| Repair Text: | From Oracle doc: Report to Oracle Customer Support. The first argument is the internal error number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | program could not allocate memory |
| Long Text: | The operating system has run out of memory. |
| Repair Text: | From Oracle doc: Take action to make more memory available to the program. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21503 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | program terminated by fatal error |
| Long Text: | A program is in an unrecoverable error state. |
| Repair Text: | From Oracle doc: Report to Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21520 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database server driver not installed |
| Long Text: | User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in. |
| Repair Text: | From Oracle doc: Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21521 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded maximum number of connections in OCI (object mode only) |
| Long Text: | User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode. |
| Repair Text: | From Oracle doc: Close some of existing and unused connections before opening more connections. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21522 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempted to use an invalid connection in OCI (object mode only) |
| Long Text: | User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to de-reference a REF obtained from a connection which has been terminated. |
| Repair Text: | From Oracle doc: Ensure that the connection exists and is still valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21523 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | functionality not supported by the server (object mode only) |
| Long Text: | User attempted to use a functionality that the server does not support. |
| Repair Text: | From Oracle doc: Upgrade the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21524 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object type mismatch |
| Long Text: | The object type of the object is different from what is specified. |
| Repair Text: | From Oracle doc: Check the type of the object and correct it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21525 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute number or (collection element at index) %s violated its constraints |
| Long Text: | Attribute value or collection element value violated its constraint. |
| Repair Text: | From Oracle doc: Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element's schema information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21526 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | initialization failed |
| Long Text: | The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value. |
| Repair Text: | From Oracle doc: Check that all NLS environment variables are well-formed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21560 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument %s is null, invalid, or out of range |
| Long Text: | The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB - 1), or when an invalid open mode is used to open a file, and so on. |
| Repair Text: | From Oracle doc: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | path expression too long |
| Long Text: | The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression. |
| Repair Text: | From Oracle doc: Pass in the correct path expression to locate the attribute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute is not an object |
| Long Text: | The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type. |
| Repair Text: | From Oracle doc: Avoid performing such operation to an attribute of built-in type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21602 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation does not support the specified typecode |
| Long Text: | The user attempts to perform an operation that does not support the specified type code. |
| Repair Text: | From Oracle doc: Use the range of valid type codes that are supported by this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21603 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | property id [%s] is invalid |
| Long Text: | The specified property ID is invalid. |
| Repair Text: | From Oracle doc: Specify a valid property ID. Valid property IDs are enumerated by OCIObjectPropId. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21604 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | property [%s] is not a property of transient or value instances |
| Long Text: | An attempt was made to get a property which applies only to persistent objects. |
| Repair Text: | From Oracle doc: Check the lifetime and only get this property for persistent objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21605 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | property [%s] is not a property of value instances |
| Long Text: | An attempt was made to get a property which applies only to persistent and transient objects. |
| Repair Text: | From Oracle doc: Check the lifetime and only get this property for persistent and transient objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not free this object |
| Long Text: | An attempt was made to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified. |
| Repair Text: | From Oracle doc: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21607 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | memory cartridge service handle not initialized |
| Long Text: | Attempt to use the handle without initializing it. |
| Repair Text: | From Oracle doc: Initialize the memory cartridge service handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21608 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duration is invalid for this function |
| Long Text: | Attempt to use a duration not valid for this function. |
| Repair Text: | From Oracle doc: Use a valid duration: a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration or external procedure duration, use OCIExtProcAllocCallMemory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21609 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | memory being resized without being allocated first |
| Long Text: | Attempt to resize memory without allocating it first. |
| Repair Text: | From Oracle doc: Allocate the memory first before resizing it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21610 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | size [%s] is invalid |
| Long Text: | Attempt to resize memory with invalid size. |
| Repair Text: | From Oracle doc: Pass in a valid size (must be a positive integer). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21611 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | key length [%s] is invalid |
| Long Text: | Attempt to use an invalid key length. |
| Repair Text: | From Oracle doc: Key length is invalid and valid range is 0 to 64. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21612 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | key is already being used |
| Long Text: | Attempt to use a key that is already used. |
| Repair Text: | From Oracle doc: Use a new key that is not yet being used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21613 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | key does not exist |
| Long Text: | Attempt to use a non-existent key. |
| Repair Text: | From Oracle doc: Use a key that already exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21614 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | constraint violation for attribute number %s |
| Long Text: | Constraints on the attribute were violated. |
| Repair Text: | From Oracle doc: Correct the value (of the attribute) so that it satisfies constraints. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21615 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | copy of an OTS (named or simple) instance failed |
| Long Text: | See following message. |
| Repair Text: | From Oracle doc: Check that no attribute value violates constraints. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21700 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object does not exist or is marked for delete |
| Long Text: | User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete. |
| Repair Text: | From Oracle doc: Re-initialize the reference to reference an existent object or unmark the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to flush objects to different servers |
| Long Text: | User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program. |
| Repair Text: | From Oracle doc: Avoid performing this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object is not instantiated or has been de-instantiated in cache |
| Long Text: | User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object. |
| Repair Text: | From Oracle doc: Check their code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the allocation duration of the object has expired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot flush an object that is not modified |
| Long Text: | See the error message. |
| Repair Text: | From Oracle doc: The object should not be flushed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot terminate cache or connection without flushing first |
| Long Text: | See the error message. |
| Repair Text: | From Oracle doc: The transaction should be aborted or committed before terminating the cache or connection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | service context is invalid |
| Long Text: | The service context that is supplied by the user is not valid. |
| Repair Text: | From Oracle doc: Establish the service context. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duration does not exist or is invalid |
| Long Text: | The duration number that is supplied by the user is not valid. |
| Repair Text: | From Oracle doc: Establish the duration or use a correct predefined duration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21707 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pin duration is longer than allocation duration |
| Long Text: | The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters. |
| Repair Text: | From Oracle doc: Use a shorter pin duration or use the null duration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21708 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inappropriate operation on a transient object |
| Long Text: | An attempt was made to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking. |
| Repair Text: | From Oracle doc: Avoid performing such operations on a transient object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21709 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot refresh an object that has been modified |
| Long Text: | An attempt was made to refresh an object that has been marked for delete, update or insert (new). |
| Repair Text: | From Oracle doc: Unmark the object before refreshing it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21710 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument is expecting a valid memory address of an object |
| Long Text: | The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object. |
| Repair Text: | From Oracle doc: Pass in a valid memory address of an object to the function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-21779 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duration not active |
| Long Text: | An attempt was made to use a duration that has been terminated. |
| Repair Text: | From Oracle doc: Avoid performing such operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | overflow error |
| Long Text: | This operation's result is above the range of Oracle number. |
| Repair Text: | From Oracle doc: Decrease the input value(s) so that the result is in the range of Oracle number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | underflow error |
| Long Text: | This operation's result is below the range of Oracle number. |
| Repair Text: | From Oracle doc: Increase the input value(s) so that the result is in the range of Oracle number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22055 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown sign flag value [%s] |
| Long Text: | Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED. |
| Repair Text: | From Oracle doc: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22056 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value [%s] is divided by zero |
| Long Text: | Given value is divided by zero. |
| Repair Text: | From Oracle doc: Modify divisor value to be non-zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22057 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad integer length [%s] |
| Long Text: | The length of the integer (that is, number of bytes) to be converted to or from an Oracle number is invalid. |
| Repair Text: | From Oracle doc: Use integer length 1, 2, 4 or 8 bytes only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22059 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buffer size [%s] is too small - [%s] is needed |
| Long Text: | The buffer to hold the resulting text string is too small. |
| Repair Text: | From Oracle doc: Provide a buffer of the required size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument [%s] is an invalid or uninitialized number |
| Long Text: | An invalid or uninitialized number is passed in. |
| Repair Text: | From Oracle doc: Use a valid number. To initialize number, call OCINumberInit(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid format text [%s] |
| Long Text: | The numeric format string for converting characters to or from an Oracle number is invalid. |
| Repair Text: | From Oracle doc: Use valid format string as documented in the Oracle Call Interface Programmer's Guide. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22062 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid input %s [%s] |
| Long Text: | The text string for converting to numbers is invalid. |
| Repair Text: | From Oracle doc: Use a valid input string as documented in the Oracle Call Interface Programmer's Guide. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22063 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | reading negative value [%s] as unsigned |
| Long Text: | An attempt was made to convert a negative number to an unsigned integer. |
| Repair Text: | From Oracle doc: Use the sign flag ORLTSB to convert a signed number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22064 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid NLS parameter %s [%s] |
| Long Text: | The NLS parameter string for converting characters to or from an Oracle number is invalid. |
| Repair Text: | From Oracle doc: Use valid format string as documented in the Oracle Call Interface Programmer's Guide. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22065 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number to text translation for the given format causes overflow |
| Long Text: | Rounding done due to the given string format causes overflow. |
| Repair Text: | From Oracle doc: Change the string format such that overflow does not occur. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22130 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buffer size [%s] is less than the required size [%s] |
| Long Text: | The size of the buffer into which the hexadecimal REF string is to be written is too small. |
| Repair Text: | From Oracle doc: Provide a buffer of the required size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22131 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hexadecimal %s length is zero |
| Long Text: | The given hexadecimal string length must be greater than zero. |
| Repair Text: | From Oracle doc: Specify a length greater than zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22132 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hexadecimal %s does not correspond to a valid REF |
| Long Text: | The given hexadecimal string is invalid. |
| Repair Text: | From Oracle doc: Provide a valid hexadecimal string which was previously returned by a call to OCIRefToHex(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22140 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | given size [%s] must be in the range of 0 to [%s] |
| Long Text: | The given resize size is invalid. |
| Repair Text: | From Oracle doc: Ensure that the given size is in the required range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | variable-length array has not been initialized |
| Long Text: | An un-initialized variable-length array is being operated upon. |
| Repair Text: | From Oracle doc: Initialize the variable-length array prior to calling this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot resize non-zero variable-length array to zero elements |
| Long Text: | An attempt was made to resize a non-zero variable-length array to 0 elements. |
| Repair Text: | From Oracle doc: Specify a non-zero size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | destination variable-length array is not initialized |
| Long Text: | The variable-length array on the right-hand-side of an assignment or the destination array of an append is not initialized. |
| Repair Text: | From Oracle doc: Initialize the destination variable-length array prior to calling this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | source variable-length array is not initialized |
| Long Text: | The variable-length array on the left-hand-side of an assignment or the source array of an append is not initialized. |
| Repair Text: | From Oracle doc: Initialize the destination variable-length array prior to calling this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | element at index [%s] does not exist |
| Long Text: | Collection element at the given index does not exist. |
| Repair Text: | From Oracle doc: Specify the index of an element which exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type code [%s] is not valid |
| Long Text: | Given type code is not valid. |
| Repair Text: | From Oracle doc: Use one of the type codes enumerated in OCITypeCode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | element at index [%s] has been previously deleted |
| Long Text: | An attempt was made to delete a non-existent collection element. |
| Repair Text: | From Oracle doc: Check for the existence of the element prior to calling this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | left hand and right hand side collections are not of same type |
| Long Text: | Left hand and right side collections are not of same type. |
| Repair Text: | From Oracle doc: Ensure that the same collection type is passed for both left hand and right hand side of this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22164 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | delete element operation is not allowed for variable-length array |
| Long Text: | An attempt was made to delete an element of a variable-length array. |
| Repair Text: | From Oracle doc: Ensure that the collection is not a variable-length array prior to calling this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22165 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | given index [%s] must be in the range of 0 to [%s] |
| Long Text: | Given index is not in the required range. |
| Repair Text: | From Oracle doc: Ensure that the given index is in the required range. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22166 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | collection is empty |
| Long Text: | Given collection is empty. |
| Repair Text: | From Oracle doc: Test if collection is empty prior to invoking this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22167 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | given trim size [%s] must be less than or equal to [%s] |
| Long Text: | Given trim size is greater than the current collection size. |
| Repair Text: | From Oracle doc: Ensure that the given size is less than or equal to the collection size prior to calling this function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22275 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid LOB locator specified |
| Long Text: | One of the following: The LOB locator was never initialized. The locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator. The locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator. An attempt was made to update the LOB in a trigger body -- LOBs in trigger bodies are read only. |
| Repair Text: | From Oracle doc: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid locator for LOB buffering |
| Long Text: | One of the following: The locator was never enabled for buffering. It is not an updated locator but is being used for a write/flush operation. |
| Repair Text: | From Oracle doc: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use two different locators to modify the same LOB |
| Long Text: | LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators. |
| Repair Text: | From Oracle doc: When using LOB buffering, modify the LOB through one LOB locator only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must update the LOB only through the LOB buffers |
| Long Text: | LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed. |
| Repair Text: | From Oracle doc: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, buffers associated with this LOB should either be flushed as necessary or buffering should be disabled. Once this is done, reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22279 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform operation with LOB buffering enabled |
| Long Text: | The operation attempted is not allowed when LOB buffering is enabled. |
| Repair Text: | From Oracle doc: If the operation is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22280 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no more buffers available for operation |
| Long Text: | One of the following: All buffers in the buffer pool have been used up by previous operations. An attempt was made to flush a LOB without any previous buffered update operations. |
| Repair Text: | From Oracle doc: For (1), flush the LOB(s) through the locator that is being used to update the LOB. For (2), write to the LOB through a locator enabled for buffering before attempting to flush buffers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform operation with an updated locator |
| Long Text: | The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the input locator; thus, the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB may be used to modify the LOB value through the LOB buffering subsystem. |
| Repair Text: | From Oracle doc: Depending on whether the modifications made through the input locator to the LOB buffering subsystem should be written to the server, either flush the buffer to write the modifications, or, disable buffering on the locator to discard the modifications. Then, reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22282 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-contiguous append to a buffering enabled LOB not allowed |
| Long Text: | The buffered write operation has an input offset value more than one byte or character past the end of the LOB. |
| Repair Text: | From Oracle doc: Specify an input offset value which is exactly one character or byte greater than the length of the LOB that you are attempting to update through a buffered write operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22285 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-existent directory or file for %s operation |
| Long Text: | An attempt was made to access a directory that does not exist, or attempted to access a file in a directory that does not exist. |
| Repair Text: | From Oracle doc: Ensure that a system object corresponding to the specified directory exists in the database dictionary, or make sure the name is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22286 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges on file or directory to perform %s operation |
| Long Text: | The user does not have the necessary access privileges on the directory alias and/or the file for the operation. |
| Repair Text: | From Oracle doc: Ask the database/system administrator to grant the required privileges on the directory alias and/or the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22287 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or modified directory occurred during %s operation |
| Long Text: | The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the database administrator since the last access. |
| Repair Text: | From Oracle doc: If you are accessing this directory for the first time, provide a valid directory name. If you have been already successful in opening a file under this directory before this error occurred, then close the file and retry the operation with a valid directory alias as modified by your database administrator. Oracle recommends that directories should be modified only during quiescent periods. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22288 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file or LOB operation %s failed%s |
| Long Text: | The operation attempted on the file or LOB failed. |
| Repair Text: | From Oracle doc: See the next error message in the error stack for more detailed information. Also, verify that the file or LOB exists and that the necessary privileges are set for the specified operation. If the error still persists, report the error to the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22289 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform %s operation on an unopened file or LOB |
| Long Text: | The file or LOB is not open for the required operation to be performed. |
| Repair Text: | From Oracle doc: Precede the current operation with a successful open operation on the file or LOB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22290 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation would exceed the maximum number of opened files or LOBs |
| Long Text: | The number of open files or LOBs has reached the maximum limit. |
| Repair Text: | From Oracle doc: Close some of the opened files or LOBs and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22291 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Open LOBs exist at transaction commit time |
| Long Text: | An attempt was made to commit a transaction with open LOBs at transaction commit time. |
| Repair Text: | From Oracle doc: Close the LOBs before committing the transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22292 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot open a LOB in read-write mode without a transaction |
| Long Text: | An attempt was made to open a LOB in read-write mode before a transaction was started. |
| Repair Text: | From Oracle doc: Start a transaction before opening the LOB in read-write mode. Ways to start a transaction include issuing a SQL DML or SELECT FOR UPDATE command. Opening the LOB in read-only mode does not require a transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22293 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOB already opened in the same transaction |
| Long Text: | An attempt was made to open a LOB that already is open in this transaction. |
| Repair Text: | From Oracle doc: Close the LOB before attempting to reopen it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22294 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot update a LOB opened in read-only mode |
| Long Text: | An attempt was made to write to or update a LOB opened in read-only mode. |
| Repair Text: | From Oracle doc: Close the LOB and reopen it in read-write mode before attempting to write to or update the LOB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type "%s"."%s" not found |
| Long Text: | An attempt was made to obtain information for a type that cannot be found. |
| Repair Text: | From Oracle doc: Check that the schema is correct and that the type has been created correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input type is not an object type |
| Long Text: | An attempt was made to obtain the supertype information for a non-object type. |
| Repair Text: | From Oracle doc: Pass in only an object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute/method/parameter "%s" not found |
| Long Text: | Type element with the given name is not found in the type. |
| Repair Text: | From Oracle doc: Check to make sure that the type element exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type "%s"."%s" already exists |
| Long Text: | An attempt was made to create a type that already exists. |
| Repair Text: | From Oracle doc: Check to make sure that the type has not been created prior to this. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22307 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation must be on a user-defined type |
| Long Text: | An attempt was made to perform an operation that is allowed only on a user-defined type, and the type is not a user-defined type. |
| Repair Text: | From Oracle doc: Check to make sure that only user-defined types are being operated on. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute with name "%s" already exists |
| Long Text: | An attempt was made to create an object type where more than one attributes have the same name. |
| Repair Text: | From Oracle doc: Check to make sure that all attribute names are unique. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type for attribute "%s" does not exist |
| Long Text: | The type of the attribute does not exist. |
| Repair Text: | From Oracle doc: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute's type in the DDL transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use two versions of the same type "%s" |
| Long Text: | The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type. |
| Repair Text: | From Oracle doc: Check that the libraries being linked with this application and use the same versions of the type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | method information mismatch in ALTER TYPE |
| Long Text: | The number of methods or the method signature do not match that of the original type declaration. This is not supported. |
| Repair Text: | From Oracle doc: Make sure the method signature stay identical for the previously declared method. Do not drop existing methods. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type "%s" does not contain a map or order function |
| Long Text: | The input type does not contain a map or order function so one cannot be returned. |
| Repair Text: | From Oracle doc: Add a map or order function to the type or catch this error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input type is not a collection type |
| Long Text: | An attempt was made to obtain information for collection types on a non-named collection type. |
| Repair Text: | From Oracle doc: Use a named collection type for the function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | typecode number is not legal as a number type |
| Long Text: | An attempt was made to use a number type code that is not valid. |
| Repair Text: | From Oracle doc: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input type is not an array type |
| Long Text: | An attempt was made to obtain the number of elements for a non-array type. |
| Repair Text: | From Oracle doc: Pass in only a named collection type which is an array. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type attribute information altered in ALTER TYPE |
| Long Text: | The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added. |
| Repair Text: | From Oracle doc: Check that all type alterations are legal. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | method does not return any result |
| Long Text: | OCITypeResult() was called on a method that does not return any results. |
| Repair Text: | From Oracle doc: Check that you are passing in the correct method descriptor, or that your method creation was done correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid parameter encountered in method %s |
| Long Text: | An invalid parameter is being passed to this method of SYS.RowType or SYS.RowSet. |
| Repair Text: | From Oracle doc: Check the parameters being passed to this method and make sure that the parameters are allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22370 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect usage of method %s |
| Long Text: | This method of SYS.RowType or SYS.RowSet is being used inappropriately. |
| Repair Text: | From Oracle doc: Check the documentation for correct usage. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | encountered 8.0.2 (Beta) VARRAY data that cannot be processed |
| Long Text: | Production Oracle8 (8.0.3 and beyond) encountered some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data. |
| Repair Text: | From Oracle doc: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then reinsert the VARRAY data. There is no provided script or tool to help automate this conversion. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pickler TDS context [%s] is not initialized |
| Long Text: | An attempt was made to use the pickler TDS context without initializing it. |
| Repair Text: | From Oracle doc: Use OCIPicklerTdsCtxInit to initialize the context. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22602 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pickler TDS handle [%s] is not well-formed |
| Long Text: | An attempt was made to use the pickler TDS handle without initializing or constructing it. |
| Repair Text: | From Oracle doc: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22603 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add an attribute to the already generated TDS handle |
| Long Text: | An attempt was made to add an attribute to the already constructed TDS. |
| Repair Text: | From Oracle doc: Use a TDS handle that is initialized but not yet constructed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22604 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TDS handle already generated |
| Long Text: | An attempt was made to generate TDS that is already generated. |
| Repair Text: | From Oracle doc: Use a TDS handle that is initialized but not yet generated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22605 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | FDO handle [%s] is not initialized |
| Long Text: | An attempt was made to use an uninitialized FDO handle. |
| Repair Text: | From Oracle doc: Use OCIPicklerFdoInit to initialize FDO handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pickler image handle [%s] is not well-formed |
| Long Text: | An attempt was made to use the image handle without initializing/ constructing it. |
| Repair Text: | From Oracle doc: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use OCIPicklerImageGenerate to generate the image before its attributes can be accessed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22607 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | image handle already generated |
| Long Text: | An attempt was made to generate image that is already generated. |
| Repair Text: | From Oracle doc: Use a image handle that is initialized but not yet generated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22608 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add an attribute to the already generated image handle |
| Long Text: | An attempt was made to add an attribute to the already constructed image. |
| Repair Text: | From Oracle doc: Use a image handle that is initialized but not yet constructed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22609 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error %s during initialization of FDO |
| Long Text: | An error occurred during FDO initialization. |
| Repair Text: | From Oracle doc: Take an action based on the specified error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22610 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while adding a scalar to the image handle |
| Long Text: | An error occurred while adding a scalar attribute to the image handle. |
| Repair Text: | From Oracle doc: Make sure image handle is initialized before adding scalar. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22611 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TDS version is not recognized |
| Long Text: | Incorrect TDS handle is passed. |
| Repair Text: | From Oracle doc: Make sure image handle is initialized with the correct TDS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22612 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TDS does not describe a collection TDS |
| Long Text: | Collection construct/access routines are being on an image but the TDS does not describe that a collection TDS. |
| Repair Text: | From Oracle doc: Make sure a collection TDS is used before invoking collection routines on the image handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22613 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buflen does not match the size of the scalar |
| Long Text: | BUFLEN is incorrect. |
| Repair Text: | From Oracle doc: Make sure BUFLEN is correct and matches the size of the scalar. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22614 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while construction the collection in the image |
| Long Text: | An error occurred during the construction of collection. |
| Repair Text: | From Oracle doc: Make sure image handle is initialized and OCIPicklerImageCollBegin is called to begin collection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22615 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute is not a collection |
| Long Text: | Collection routine is invoked upon a non-collection attribute. |
| Repair Text: | From Oracle doc: Make sure attribute is a collection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22616 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | image is not of Oracle 8.1 format |
| Long Text: | The function being invoked is applicable only for 8.1 images. |
| Repair Text: | From Oracle doc: Make sure image is of 8.1 format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22617 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while accessing the image handle collection |
| Long Text: | An error occurred while accessing collection in the image handle. |
| Repair Text: | From Oracle doc: Make sure image is initialized correctly and the collection is constructed properly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22618 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute is a BAD NULL in the image handle |
| Long Text: | The attribute in question is probably the attribute of a null embedded image. |
| Repair Text: | From Oracle doc: Make sure attribute number is valid or it is NULL or NOT NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22619 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | all collection elements have already been accessed |
| Long Text: | An attempt was made to access a collection element after all the collection elements are already accessed. |
| Repair Text: | From Oracle doc: This function should not be invoked any more. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22620 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buffer size too small to hold the value |
| Long Text: | Buffer size is not enough to hold the value. Most likely while doing the character set conversion, a bigger buffer is needed. |
| Repair Text: | From Oracle doc: Pass in a bigger buffer. If the client character set format differs from that of server, doing the conversion may result in 4X expansion. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22621 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error transfering an object from the agent |
| Long Text: | An error was returned from the pickler routines on the agent side. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid user-defined type |
| Long Text: | An attempt was made to use an incomplete type as a constructor. |
| Repair Text: | From Oracle doc: Complete the type definition before using it in a query. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid object row variable |
| Long Text: | The specified object row variable is not available in the scope of name resolution. |
| Repair Text: | From Oracle doc: Verify the specified object row variable is correct, or use an object row variable visible in scope. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot update attributes of packed ADTs in SQL |
| Long Text: | An attempt was made to update an attribute of a packed ADT column in an UPDATE statement. |
| Repair Text: | From Oracle doc: Use an unpacked ADT column, OR update the entire ADT instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object type contains zero attributes |
| Long Text: | An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context. |
| Repair Text: | From Oracle doc: Specify a valid object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote operations not permitted on object tables or user-defined type columns |
| Long Text: | An attempt was made to perform queries or DML operations on remote object tables or on remote table columns whose type is one of object, REF, nested table or VARRAY. |
| Repair Text: | From Oracle doc: Remove the reference to remote tables in the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22805 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot insert NULL object into object tables or nested tables |
| Long Text: | An attempt was made to insert a NULL object into an object table or a Nested Table. |
| Repair Text: | From Oracle doc: Ensure that a non-NULL object is inserted into the table or insert an object with attributes whose values are NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22806 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not an object or REF |
| Long Text: | An attempt was made to extract an attribute from an item that is neither an object nor a REF. |
| Repair Text: | From Oracle doc: Use an object type or REF type item and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22807 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot resolve to a scalar type or a collection type |
| Long Text: | Invalid use of a non-scalar (for example, object type) item. |
| Repair Text: | From Oracle doc: Change the item's data type and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22808 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REF dereferencing not allowed |
| Long Text: | An attempt was made to access an object type's attributes by de-referencing a REF item. |
| Repair Text: | From Oracle doc: Make the item an object type instead of a REF to an object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22809 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | nonexistent attribute |
| Long Text: | An attempt was made to access a non-existent attribute of an object type. |
| Repair Text: | From Oracle doc: Check the attribute reference to see if it is valid. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify object attributes with REF dereferencing |
| Long Text: | An attempt was made to modify the attributes an object by de-referencing a REF column in an UPDATE statement. |
| Repair Text: | From Oracle doc: Update the table containing the object that the REF points to, or change the REF column to an object type column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot access attributes of packed adts in SQL |
| Long Text: | Attempt to access an attribute of a packed ADT column/table. |
| Repair Text: | From Oracle doc: Use an unpacked ADT or retrieve the entire ADT instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot reference nested table column's storage table |
| Long Text: | An attempt to access the nested table column's storage table is not allowed in the given context. |
| Repair Text: | From Oracle doc: Issue the statement against the parent table containing the nested table column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operand value exceeds system limits |
| Long Text: | Object or Collection value was too large. The size of the value might have exceeded 30k in a SORT context, or the size might be too big for available memory. |
| Repair Text: | From Oracle doc: Choose another value and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22814 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute or element value is larger than specified in type |
| Long Text: | Value provided for the object type attribute or collection element exceeded the size specified in the type declaration. |
| Repair Text: | From Oracle doc: Choose another value and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported feature with RETURNING clause |
| Long Text: | RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and dereferencing inside returning clause. |
| Repair Text: | From Oracle doc: Use separate SELECT statements to get the values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22817 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subquery not allowed in the default clause |
| Long Text: | An attempt was made to use a subquery in the column default clause expression. |
| Repair Text: | From Oracle doc: Remove the subquery from the default clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22818 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subquery expressions not allowed here |
| Long Text: | An attempt was made to use a subquery expression where these are not supported. |
| Repair Text: | From Oracle doc: Rewrite the statement without the subquery expression. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22819 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scope of input value does not correspond to the scope of the target |
| Long Text: | An attempt was made to operate on a REF value scoped to a different table than the expected one. |
| Repair Text: | From Oracle doc: Use a REF which is scoped to the expected table and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22850 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate LOB storage option specificed |
| Long Text: | A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) was specified more than once. |
| Repair Text: | From Oracle doc: Specify all LOB storage options only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22851 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CHUNK LOB storage option value |
| Long Text: | The specified CHUNK LOB storage option value must be an integer. |
| Repair Text: | From Oracle doc: Choose an appropriate integer value and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22852 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid PCTVERSION LOB storage option value |
| Long Text: | The specified PCTVERSION LOB storage option value must be an integer. |
| Repair Text: | From Oracle doc: Choose an appropriate integer value and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22853 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid LOB storage option specification |
| Long Text: | A LOB storage option was not specified. |
| Repair Text: | From Oracle doc: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX as part of the LOB storage clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22854 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for LOB storage index |
| Long Text: | A valid LOB store index option was not specified. |
| Repair Text: | From Oracle doc: Specify one of (INITTRANS, MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22855 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | optional name for LOB storage segment incorrectly specified |
| Long Text: | The optional name for LOB storage segment was specified with multiple columns in the column list. |
| Repair Text: | From Oracle doc: Specify each column LOB storage only with optional name(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22856 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add columns to object tables |
| Long Text: | An attempt was made to add columns to an object table. Object tables cannot be altered to add columns since its definition is based on an object type. |
| Repair Text: | From Oracle doc: Create a new type with additional attributes, and use the new type to create an object table. The new object table will have the desired columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22857 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify columns of object tables |
| Long Text: | An attempt was made to alter the object table by modifying existing columns. An object table cannot be altered to modify existing columns since it is based on an object type. The table definition must be in sync with the corresponding type. |
| Repair Text: | From Oracle doc: Create a new type with the desired attribute types and use it to create an object table. The new object table will have the desired columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22858 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid alteration of datatype |
| Long Text: | An attempt was made to modify the column type to object, REF, nested table, VARRAY or LOB type. |
| Repair Text: | From Oracle doc: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22859 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid modification of columns |
| Long Text: | An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type. |
| Repair Text: | From Oracle doc: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22860 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object type expected |
| Long Text: | An attempt was made to create an object table using a non- object type, or to create a column that is a REF to a non-object type. |
| Repair Text: | From Oracle doc: Use a valid object type in the table or column definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22861 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid user-defined type |
| Long Text: | An attempt was made to create a column or object table of a non-existent type. |
| Repair Text: | From Oracle doc: Specify a valid type in the table or column definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22862 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified object identifier doesn't match existing object identifier |
| Long Text: | An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type of the same name. |
| Repair Text: | From Oracle doc: Specify the correct object identifier or leave it out of the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22863 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | synonym for datatype %s.%s not allowed |
| Long Text: | A synonym specification for a datatype is not supported. |
| Repair Text: | From Oracle doc: Do not use the synonym for the datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22864 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot ALTER or DROP LOB indexes |
| Long Text: | An attempt was made to ALTER or DROP a LOB index. |
| Repair Text: | From Oracle doc: Do not operate directly on the system-defined LOB index. Perform operations on the corresponding LOB column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22865 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | more than one column specified |
| Long Text: | An attempt was made to specify multiple columns where only one is allowed. |
| Repair Text: | From Oracle doc: Specify a single column and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22866 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | default character set is of varying width |
| Long Text: | A character LOB was defined but the default character set is not fixed width. |
| Repair Text: | From Oracle doc: Ensure that the character set is of fixed width before defining character LOBs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22868 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table with LOBs contains segments in different tablespaces |
| Long Text: | An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment. |
| Repair Text: | From Oracle doc: Find table(s) with LOB columns which have non-table segments in this tablespace. Drop these tables and reissue drop tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22869 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | depth of type dependency hierarchy exceeds maximum limit |
| Long Text: | The type dependency hierarchy was structured to have depth greater than 1024. |
| Repair Text: | From Oracle doc: Restructure the type dependency hierarchy to a shorter depth. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22870 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER TYPE with REPLACE option a non-object type |
| Long Text: | An attempt was made to perform ALTER TYPE with REPLACE option a non-object type. |
| Repair Text: | From Oracle doc: Drop the non-object type first, then re-create it as an object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22871 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTER TYPE with REPLACE is not allowed for pure incomplete types |
| Long Text: | An attempt was made to perform ALTER TYPE with REPLACE option for a pure incomplete type. |
| Repair Text: | From Oracle doc: Completely define the original type, before using the ALTER TYPE with REPLACE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22872 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OID INDEX clause not allowed on tables with primary key based object identifiers |
| Long Text: | An attempt was made to create an OID INDEX on a table with primary key-based object identifiers. |
| Repair Text: | From Oracle doc: Remove the OID INDEX clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22873 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | primary key not specified for primary key based object table |
| Long Text: | An attempt was made to create a primary key based object table without specifying a primary key. |
| Repair Text: | From Oracle doc: Specify a primary key and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22874 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attribute "%s" is not part of the type "%s" |
| Long Text: | Attribute specified in the USER_DEFINED clause is not an attribute of the REF type. |
| Repair Text: | From Oracle doc: Ensure that the name specified in the USER_DEFINED clause is the name of a valid attribute of the REF type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22875 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop primary key of an object table whose object identifier is primary key based |
| Long Text: | An attempt was made to drop the primary key of an object table which has a primary key based object identifier. |
| Repair Text: | From Oracle doc: Remove the drop primary key clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22876 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this user-defined type is not allowed or it cannot be used in this context |
| Long Text: | An attempt was made to create a kind of user-defined type which is not allowed, or an attempt to create table columns or use default constructor with a type on which these are not supported. |
| Repair Text: | From Oracle doc: Ensure that the type is permitted in this context. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22877 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option specified for a HASH partition or subpartition of a LOB column |
| Long Text: | One or more invalid options were encountered while parsing the physical attributes of a LOB partition or subpartition. Either the LOB partition is in a table partitioned using the HASH method, or the LOB subpartition is in a table subpartitioned using the HASH method. TABLESPACE is the only valid option for a HASH partition or subpartition. |
| Repair Text: | From Oracle doc: Remove the invalid option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22878 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate LOB partition or subpartition specified |
| Long Text: | An attempt was made was made to specify a partition or subpartition that has already been specified for the LOB column. |
| Repair Text: | From Oracle doc: Remove the duplicate specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22879 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use the LOB INDEX clause for partitioned tables |
| Long Text: | An attempt was made to specify a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned table. |
| Repair Text: | From Oracle doc: Remove the LOB INDEX clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22880 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid REF |
| Long Text: | An invalid REF was accessed. |
| Repair Text: | From Oracle doc: Modify the REF and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22881 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dangling REF |
| Long Text: | The object corresponding to the REF that was accessed does not exist. |
| Repair Text: | From Oracle doc: Ensure that the REF value is pointing to an existing object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22882 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object creation failed |
| Long Text: | The object cannot be created in the database. |
| Repair Text: | From Oracle doc: Check to see if the object table exists and the object size is not too big. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22883 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object deletion failed |
| Long Text: | The object could not be deleted from the database. |
| Repair Text: | From Oracle doc: Check to see if the object table exists. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22884 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object modification failed |
| Long Text: | The object could not be modified in the database. |
| Repair Text: | From Oracle doc: Check to see if the object table exists and the object size is not too big. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22885 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot get REF to a non-persistent object |
| Long Text: | An attempt was made to get a REF for something other than an object in an object table. REFs can only be taken for objects in object tables. |
| Repair Text: | From Oracle doc: Rewrite the query to obtain REF values from object tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22886 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scoped table "%s" in schema "%s" is not an object table |
| Long Text: | The scoped table specified for a REF column is not an object table. |
| Repair Text: | From Oracle doc: Ensure that the scoped table is an object table. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22887 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type of REF column is not the same as that of its scoped table |
| Long Text: | The type specified for the REF column and the type specified for the scope table are different. |
| Repair Text: | From Oracle doc: Ensure that the types of a REF column and its scoped table are the same. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22888 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate SCOPE clauses for a REF column |
| Long Text: | Multiple SCOPE clauses were specified for a single REF column. |
| Repair Text: | From Oracle doc: Remove the duplicate SCOPE clauses and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22889 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REF value does not point to scoped table |
| Long Text: | An attempt was made to insert a REF value that does not point to the scoped table. |
| Repair Text: | From Oracle doc: Ensure that the REF values point to the scoped table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22890 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify name for REF column constraint |
| Long Text: | An attempt was made to specify a constraint name for a constraint on a REF column. |
| Repair Text: | From Oracle doc: Remove the constraint name and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22891 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot have multiple columns in REF constraint |
| Long Text: | An attempt was made to specify multiple columns in a single REF constraint. |
| Repair Text: | From Oracle doc: Specify separate constraints for each column and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22892 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scoped table "%s" does not exist in schema "%s" |
| Long Text: | The scoped table specified for a REF column does not exist. |
| Repair Text: | From Oracle doc: Ensure that the scoped table exists and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22893 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | constraint can be specified only for REF columns |
| Long Text: | The constraint specified does not apply to non-REF columns. |
| Repair Text: | From Oracle doc: Remove the constraint and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22894 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot add constraint on existing unscoped REF columns of non-empty tables |
| Long Text: | An attempt was made to add a constraint to existing unscoped REF columns of a table which contains one or more rows. |
| Repair Text: | From Oracle doc: Remove the constraint specification or add the constraint after emptying the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22895 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referenced table "%s" in schema "%s" is not an object table |
| Long Text: | The referenced table specified for a REF column is not an object table. |
| Repair Text: | From Oracle doc: Ensure that the referenced table is an object table. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22896 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot have both scope and referential constraint on REF column "%s" |
| Long Text: | REF column has both a referential and a scope constraint. A referential constraint implies a scope constraint. |
| Repair Text: | From Oracle doc: Remove either the referential or scope constraint and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22897 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no scope clause specified for user-defined REF column "%s" |
| Long Text: | User-defined REF column does not have a scope constraint. |
| Repair Text: | From Oracle doc: Specify a scope constraint for the user-defined REF column and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22898 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | existing scope clause on "%s" points to a table other than the one mentioned in the referential constraint |
| Long Text: | Table mentioned in the referential integrity constraint is different from the scope table of the REF column. |
| Repair Text: | From Oracle doc: Specify the scope table of the REF column in the referential integrity constraint and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22899 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify both scope and rowid constraint on ref column |
| Long Text: | An attempt was made to specify both a scope and a ROWID constraint on a REF column. |
| Repair Text: | From Oracle doc: Remove either the ROWID or scope constraint and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22900 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the SELECT list item of THE subquery is not a collection type |
| Long Text: | The THE subquery must SELECT a nested table or VARRAY item. |
| Repair Text: | From Oracle doc: Change the subquery to SELECT a nested table or VARRAY item. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22901 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot compare nested table or VARRAY or LOB attributes of an object type |
| Long Text: | Comparison of nested table or VARRAY or LOB attributes of an object type was attempted in the absence of a MAP or ORDER method. |
| Repair Text: | From Oracle doc: Define a MAP or ORDER method for the object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22902 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CURSOR expression not allowed |
| Long Text: | CURSOR on a subquery is allowed only in the top-level SELECT list of a query. |
| Repair Text: | From Oracle doc: Remove the CURSOR expression and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22903 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MULTISET expression not allowed |
| Long Text: | MULTISET expressions are allowed only inside a CAST to a nested table or VARRAY type. |
| Repair Text: | From Oracle doc: put the MULTISET (subquery) expression inside a CAST to a nested table or VARRAY type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22904 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid reference to a nested table column |
| Long Text: | An invalid reference was made to a nested table column. |
| Repair Text: | From Oracle doc: Remove invalid reference to the nested table column and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22905 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot access rows from a non-nested table item |
| Long Text: | An attempt was made to access rows of an item whose type is not known at parse time or that is not of a nested table type. |
| Repair Text: | From Oracle doc: Use CAST to cast the item to a nested table type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22906 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform DML on expression or on nested table view column |
| Long Text: | An attempt was made to perform a DML on an expression or on a nested table view column where a nested table column of a base table is expected. |
| Repair Text: | From Oracle doc: Only nested table column of a base table is allowed in the DML. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22907 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CAST to a type that is not a nested table or VARRAY |
| Long Text: | An attempt was made to CAST to a type that is not a nested table or VARRAY. |
| Repair Text: | From Oracle doc: Respecify CAST to a nested table or VARRAY type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22908 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | reference to NULL table value |
| Long Text: | The evaluation of the THE subquery or nested table column resulted in a NULL value implying a NULL table instance. The THE subquery or nested table column must identify a single non-NULL table instance. |
| Repair Text: | From Oracle doc: Ensure that the evaluation of the THE subquery or nested table column results in a single non-null table instance. If happening in the context of an INSERT statement where the THE subquery is the target of an insert, then ensure that an empty nested table instance is created by updating the nested table column of the parent table's row specifying an empty nested table constructor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22909 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded maximum VARRAY limit |
| Long Text: | The total number of elements used in VARRAY construction exceeds the specified VARRAY limit. |
| Repair Text: | From Oracle doc: Do not use the more than the specified limit of elements for VARRAY construction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22910 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify schema name for nested tables |
| Long Text: | Table name was qualified with schema name in the nested table column's (or attribute's) storage clause. |
| Repair Text: | From Oracle doc: Respecify the nested table item's storage clause without the schema name qualification. By default, the storage table for the nested table item is created in the same schema as the containing table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22911 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate storage specification for the nested table item |
| Long Text: | The storage clause is specified more than once for the NESTED TABLE column. |
| Repair Text: | From Oracle doc: Remove the duplicate storage specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22912 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified column or attribute is not a nested table type |
| Long Text: | The storage clause is specified for a column or attribute that is not a nested table column or attribute. |
| Repair Text: | From Oracle doc: Specify a valid nested table column or attribute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22913 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must specify table name for nested table column or attribute |
| Long Text: | The storage clause is not specified for a nested table column or attribute. |
| Repair Text: | From Oracle doc: Specify the nested table storage clause for the nested table column or attribute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22914 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DROP of nested tables not supported |
| Long Text: | An attempt was made to DROP a nested table. |
| Repair Text: | From Oracle doc: Nested tables cannot be explicitly dropped. nested tables can only be dropped by dropping their containing parent table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22915 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot ALTER nested tables to ADD/MODIFY columns |
| Long Text: | An attempt was made to ADD or MODIFY columns of a nested table. Columns cannot be added or modified for a nested table. |
| Repair Text: | From Oracle doc: Instead, alter the parent table's nested table column to cause any such change. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22916 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot do an exact FETCH on a query with Nested cursors |
| Long Text: | Exact FETCH on a query was specified which is not allowed if the query returns any cursors. |
| Repair Text: | From Oracle doc: Do not use an exact FETCH. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22917 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | use VARRAY to define the storage clause for this column or attribute |
| Long Text: | Not using VARRAY to define storage clause for VARRAY column or attribute. |
| Repair Text: | From Oracle doc: Specify VARRAY before the column storage clause and resubmit the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22918 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified column or attribute is not a VARRAY type |
| Long Text: | An attempt was made to define a VARRAY storage clause for a column or attribute which is not VARRAY type. |
| Repair Text: | From Oracle doc: Specify VARRAY storage clause for a VARRAY column or attribute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22919 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dangling REF error or lock object failed for no wait request |
| Long Text: | The error could be one of the following: the object corresponding to the REF does not exist or the object was locked by another user and the lock with nowait request failed. |
| Repair Text: | From Oracle doc: Ensure that the REF value is pointing to an existing object or issue a lock request without the nowait option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22920 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | row containing the LOB value is not locked |
| Long Text: | The row containing the LOB value must be locked before updating the LOB value. |
| Repair Text: | From Oracle doc: Lock the row containing the LOB value before updating the LOB value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22921 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | length of input buffer is smaller than amount requested |
| Long Text: | The buffer length is not big enough to hold the amount of data requested. |
| Repair Text: | From Oracle doc: Verify that the number of bytes/characters specified in the input amount parameter is not bigger than the number of bytes specified in the input buffer length parameter. Allocate more space for the input buffer if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22922 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | nonexistent LOB value |
| Long Text: | The LOB value associated with the input locator does not exist. The information in the locator does not refer to an existing LOB. |
| Repair Text: | From Oracle doc: Repopulate the locator by issuing a SELECT statement and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22923 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | amount of data specified in streaming LOB write is 0 |
| Long Text: | An attempt was made to write LOB value via the streaming mechanism (that is, unlimited write) but the input amount of data to stream was specified as 0. Thus, the user is trying to write 0 bytes to the LOB value. |
| Repair Text: | From Oracle doc: Write more than 0 bytes to the LOB value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22924 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot too old |
| Long Text: | The version of the LOB value needed for the consistent read was already overwritten by another writer. |
| Repair Text: | From Oracle doc: Use a larger version pool. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22925 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation would exceed maximum size allowed for a LOB value |
| Long Text: | An attempt was made to write too much data to the LOB value. LOB size is limited to 4 gigabytes. |
| Repair Text: | From Oracle doc: Either start writing at a smaller LOB offset or write less data to the LOB value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22926 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified trim length is greater than current LOB value's length |
| Long Text: | The input length for which to trim the LOB value to is greater than the current length of the LOB value. |
| Repair Text: | From Oracle doc: May not need to trim the LOB value because it's already smaller than the trim length specified. Or, if trimming the LOB value really is required, use a smaller trim length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22927 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid LOB locator specified |
| Long Text: | One of the following: The LOB locator was never initialized. The locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator. The locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator. An attempt was made to update the LOB in a trigger body -- LOBs in trigger bodies are read only. |
| Repair Text: | From Oracle doc: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22928 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid privilege on directories |
| Long Text: | An attempt was made to grant or revoke an invalid privilege on a directory. |
| Repair Text: | From Oracle doc: Only CREATE, DELETE, READ and WRITE privileges can be granted or revoked on directories. Do not grant or revoke other privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22929 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or missing directory name |
| Long Text: | The required directory name is invalid or missing. |
| Repair Text: | From Oracle doc: Specify a valid name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22930 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | directory does not exist |
| Long Text: | An attempt was made to access a directory that does not exist. |
| Repair Text: | From Oracle doc: Make sure the name is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22950 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot ORDER objects without MAP or ORDER method |
| Long Text: | An object type must have a MAP or ORDER method defined for all comparisons other than equality and inequality comparisons. |
| Repair Text: | From Oracle doc: Define a MAP or ORDER method for the object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22951 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL returned by ORDER method |
| Long Text: | ORDER method used to compare two object values returned NULL which is not allowed. |
| Repair Text: | From Oracle doc: Redefine the ORDER method to not return a NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22970 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name does not correspond to an object view |
| Long Text: | Either the expression is not a view name or the name specified does not correspond to an object view. |
| Repair Text: | From Oracle doc: Replace the expression with the name of an object view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22971 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid datatype for PRIMARY KEY-based object identifier |
| Long Text: | When creating an object view, the datatype of an expression in the WITH OBJECT OID clause is not allowed for PRIMARY KEY-based OID. |
| Repair Text: | From Oracle doc: Replace the expression with one of appropriate scalar datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22972 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL value not allowed in PRIMARY KEY-based object identifier |
| Long Text: | A value constituting the PRIMARY KEY-based object identifier is NULL. |
| Repair Text: | From Oracle doc: Ensure the expressions in MAKE_REF system function or attributes in the WITH OBJECT OID clause of an object view do not evaluate to NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22973 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | size of object identifier exceeds maximum size allowed |
| Long Text: | Size of the PRIMARY KEY-based object identifier of an object view exceeded the maximum size of 65535 bytes. |
| Repair Text: | From Oracle doc: Specify fewer or smaller PRIMARY KEY attributes in the WITH object OID clause when creating the object view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22974 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing WITH OBJECT OID clause |
| Long Text: | WITH OBJECT OID clause was not specified when creating an object view. |
| Repair Text: | From Oracle doc: Specify the WITH OBJECT OID clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22975 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a PRIMARY KEY-based REF to this object view |
| Long Text: | The object view specified in the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be created for such a view. |
| Repair Text: | From Oracle doc: Specify an object view that has a PRIMARY KEY-based object identifier in the MAKE_REF function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22976 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect number of arguments to MAKE_REF |
| Long Text: | Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view. |
| Repair Text: | From Oracle doc: Specify all the necessary arguments for MAKE_REF. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22977 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid attribute |
| Long Text: | Either the attribute name is missing in the WITH OBJECT OID clause or it is invalid. |
| Repair Text: | From Oracle doc: Specify a valid attribute of the object type of the object view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22978 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only simple attribute name is allowed in the WITH OBJECT OID clause |
| Long Text: | An attempt was made to specify a Nested attribute in the WITH OBJECT OID clause. |
| Repair Text: | From Oracle doc: Specify a top-level attribute of the object type of the object view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22979 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot INSERT object view REF or user-defined REF |
| Long Text: | An attempt was made to insert an object view REF or user-defined REF in a REF column created to store system generated REF values. |
| Repair Text: | From Oracle doc: Make sure the REF to be inserted is not from an object view or from a user-defined REF column |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22980 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must specify a set of attributes for the WITH OBJECT OID clause |
| Long Text: | The WITH OBJECT OID DEFAULT clause was used, but the underlying view or table does not have a OID. |
| Repair Text: | From Oracle doc: Specify attributes for the WITH OBJECT OID clause to create a primary key based object identifier for the object view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22990 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOB locators cannot span transactions |
| Long Text: | A LOB locator selected in one transaction cannot be used in a different transaction. |
| Repair Text: | From Oracle doc: Reselect the LOB locator and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22991 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient space allocated for argument %s |
| Long Text: | The data to be returned in the argument is greater than the amount of space allocated for the argument. |
| Repair Text: | From Oracle doc: Allocate more space for the argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22992 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use LOB locators selected from remote tables |
| Long Text: | A remote LOB column cannot be referenced. |
| Repair Text: | From Oracle doc: Remove references to LOBs in remote tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22993 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified input amount is greater than actual source amount |
| Long Text: | For LOB write, the amount of data received is different from the amount that was indicated would be sent. For LOB copy and load from file, the end of the source LOB/FILE value was reached before the specified input amount was copied/loaded. |
| Repair Text: | From Oracle doc: (1) will happen when using OCI's piecewise mechanism with polling or with a callback function. Modify the code either to send the amount specified or to pass 0 as the input amount so that any amount of data can be sent. (2) will happen if the specified input amount is too large for the source LOB/FILE given the starting source offset. Either decrease the starting source offset, or decrease the amount to copy/load. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22994 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | source offset is beyond the end of the source LOB |
| Long Text: | The source offset for a LOB COPY or LOB LOADFROMFILE is beyond the end of the source LOB. |
| Repair Text: | From Oracle doc: Check the length of the LOB and then adjust the source offset. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22995 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TABLESPACE DEFAULT option is invalid in this context |
| Long Text: | TABLESPACE DEFAULT option can be specified for LOB columns only in the following contexts: at the table level for a partitioned table at the partition level for a composite partition An attempt was made to use the TABLESPACE DEFAULT option in a different context. |
| Repair Text: | From Oracle doc: Remove the TABLESPACE DEFAULT option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22996 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NEXT extent size is smaller than LOB chunksize |
| Long Text: | An attempt was made to create or alter a LOB segment so that its NEXT extent size was less than the LOB chunk size. |
| Repair Text: | From Oracle doc: Specify a NEXT extent size that is greater than or equal to the LOB chunk size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-22997 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | VARRAY stored as LOB is not specified at the table level |
| Long Text: | An attempt was made to specify a VARRAY column to be stored as LOB at the partition/subpartition level in a partition maintenance or a move table statement. However, the VARRAY column was not specified to be stored as LOB at the table level when the table was created. |
| Repair Text: | From Oracle doc: Specify the VARRAY column to be stored as LOB at the table level when the table is created. Alternatively, do not specify the VARRAY column to be stored as LOB at the partition/subpartition level if it is not specified at the table level when the table is created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | The stored procedure RAISE_SYSTEM_ERROR was called which causes this error to be generated. |
| Repair Text: | From Oracle doc: Correct the problem as described in the error message or contact the application administrator or database administrator for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | mixed use of deferred rpc destination modes |
| Long Text: | Replication catalog determined deferred RPC destinations were mixed with destination determined by other mechanisms in the same transaction. |
| Repair Text: | From Oracle doc: Do not mix destination types in the same transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | application raised communication failure during deferred RPC |
| Long Text: | An application declared a communication failure during a deferred RPC. |
| Repair Text: | From Oracle doc: Retry the application when communication is restored. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | application raised generic exception during deferred RPC |
| Long Text: | An application declared a generic failure during a deferred RPC. |
| Repair Text: | From Oracle doc: Determined by the application. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | malformed deferred rpc at arg %s of %s in call %s, in tid %s |
| Long Text: | A deferred RPC call was issued without the correct number of arguments as determined by the count parameter to DBMS_DEFER.CALL. |
| Repair Text: | From Oracle doc: Be sure the number of arguments matches the count. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal deferred RPC error: %s |
| Long Text: | An internal error occurred in deferred RPC. |
| Repair Text: | From Oracle doc: Report the error and other information to support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | schema %s does not exist |
| Long Text: | The schema name was null or misspelled, or the schema does not exist locally. |
| Repair Text: | From Oracle doc: Specify the schema correctly, or create it with CREATE USER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23307 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replicated schema %s already exists |
| Long Text: | The given database already replicates the given schema. |
| Repair Text: | From Oracle doc: Choose a different schema or a different database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23308 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s.%s does not exist or is invalid |
| Long Text: | The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status. |
| Repair Text: | From Oracle doc: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s.%s of type %s exists |
| Long Text: | An object in the same name space exists, perhaps with a different type or shape, or the same object has already been registered as an REPOBJECT in another object group. |
| Repair Text: | From Oracle doc: Remove the offending object with the SQL DROP command, unregister the offending object with DBMS_REPCAT.DROP_MASTER_REPOBJECT(), or reinvoke the request using TRUE for a boolean parameter such as retry or USE_EXISTING_OBJECT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object group %s.%s is not quiesced |
| Long Text: | The requested operation requires the object group to be suspended. |
| Repair Text: | From Oracle doc: Invoke SUSPEND_MASTER_ACTIVITY at the REPGROUP's MASTERDEF, wait until the status has changed to quiesced, and then retry the original request. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23312 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not the masterdef according to %s |
| Long Text: | The group name is null, the group name is misspelled, the invocation or given database is not the MASTERDEF, or one of the masters does not believe the invocation database is the MASTERDEF. |
| Repair Text: | From Oracle doc: If the given group name and MASTERDEF were both correct, connect to the MASTERDEF and retry the request, or relocate the MASTERDEF at the (errant) databases using RELOCATE_MASTERDEF. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object group %s.%s is not mastered at %s |
| Long Text: | The group name is null, the group name is misspelled, the invocation database is not a master, or the invocation database does not believe the given database is a master. |
| Repair Text: | From Oracle doc: If the given group name was correct, connect to a current master and retry the request, make the invocation database a master with ADD_MASTER_DATABASE, or use SWITCH_SNAPSHOT_MASTER if the invocation database is a snapshot site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database is not a snapshot site for %s.%s |
| Long Text: | The invocation database is not a snapshot database for the given object group. |
| Repair Text: | From Oracle doc: Connect to the desired snapshot database and retry the request, or make the invocation database a snapshot site with CREATE_SNAPSHOT_REPSCHEMA or CREATE_SNAPSHOT_REPGROUP. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | repcatlog version or request %s is not supported by version %s |
| Long Text: | Either incompatible REPCAT versions are used, or a REPCATLOG record has been corrupted. |
| Repair Text: | From Oracle doc: Convert the master to a compatible version of REPCAT or retry the request. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the masterdef is %s |
| Long Text: | The requested operation is not permitted on a MASTERDEF site. |
| Repair Text: | From Oracle doc: Relocate the MASTERDEF to another master and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a communication failure has occurred |
| Long Text: | The remote database is inaccessible. |
| Repair Text: | From Oracle doc: Ensure the remote database is running, the communications network is functioning, and the appropriate database links are present. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a ddl failure has occurred |
| Long Text: | User-supplied or system-generated DDL did not execute successfully. |
| Repair Text: | From Oracle doc: Examine DDL, database state, REPCATLOG, and ALL_ERRORS to determine why the failure occurred. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter value %s is not appropriate |
| Long Text: | The given value of a parameter is either null, misspelled, or not supported. |
| Repair Text: | From Oracle doc: Refer to the documentation and use parameter values that are appropriate for the given situation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23320 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the request failed because of values %s and %s |
| Long Text: | A missing DDL record for a REPCATLOG record, or inconsistency in REPCAT views. |
| Repair Text: | From Oracle doc: Retry the request, or make the views consistent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Pipename may not be null |
| Long Text: | You called DBMS_PIPE with a null pipe name. |
| Repair Text: | From Oracle doc: Find out the name of the pipe and call function with non-null pipe name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Privilege error accessing pipe |
| Long Text: | You either tried to create a pipe that already existed and belonged to someone else, or remove a pipe that you were not authorized to use, or put a message into a pipe that you were not authorized for, or get a message from a pipe that you were not authorized for. |
| Repair Text: | From Oracle doc: You may have to use a different pipe name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23323 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter length exceeds deferred RPC limits |
| Long Text: | A deferred RPC parameter was longer than the deferred RPC limits of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw parameters. |
| Repair Text: | From Oracle doc: Use smaller parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23324 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error %s, while creating deferror entry at "%s" with error %s |
| Long Text: | The given error was encountered while attempting to create a DEFERROR entry for the give error code and the give database. |
| Repair Text: | From Oracle doc: Correct the cause of the given error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23325 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter type is not %s |
| Long Text: | A conflict resolution priority function was given a type different than the type assigned to the priority group; or the priority group has no type assigned or a function; or DBMS_DEFER_SYS_QUERY was called to retrieve a deferred RPC parameter from the deferred RPC queue, but the type of the parameter does not match the return type of the function. |
| Repair Text: | From Oracle doc: Use the function corresponding to the parameter type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23326 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object group %s.%s is quiesced |
| Long Text: | Either SUSPEND_MASTER_ACTIVITY has been called before the object group has resumed normal operation or a (deferred) RPC operation was attempted while the object group was quiesced. |
| Repair Text: | From Oracle doc: If SUSPEND_MASTER_ACTIVITY has been called and a RESUME_MASTER_ACTIVITY request is pending, wait until it completes, and then reinvoke SUSPEND_MASTER_ACTIVITY. Otherwise, resume database activity with the RESUME_MASTER_ACTIVITY call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23327 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | imported deferred rpc data does not match %s of importing db |
| Long Text: | Deferred RPC queues were imported from a database with a different global name or operating system than importing database. |
| Repair Text: | From Oracle doc: Deferred RPC data should only be imported into a database with the same global name and hardware and operating system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23328 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot base table "%s"."%s" differs from master table "%s"."%s" |
| Long Text: | When creating a snapshot through REPCAT, the snapshot base table name did not match a replicated table name at the master. |
| Repair Text: | From Oracle doc: Change the snapshot DDL to use the same base table as the replicated table name at the master. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23329 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | successful user-provided ddl but no snapshot "%s"."%s" |
| Long Text: | The DDL provided by the user to create a snapshot was executed without error, but snapshot does not exist. |
| Repair Text: | From Oracle doc: Manually back-out the DDL, and reregister with matching DDL and snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23330 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column group %s already exists |
| Long Text: | The column group was already registered in the object group. |
| Repair Text: | From Oracle doc: Use a column group name not yet registered in the replicated object group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23331 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column group %s does not exist |
| Long Text: | The given column group is either null, misspelled or not registered. |
| Repair Text: | From Oracle doc: Use a registered column group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23332 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | group %s is in use; cannot drop |
| Long Text: | The given column group or priority group is being used to resolve conflicts. |
| Repair Text: | From Oracle doc: Call DBMS_REPCAT procedures DROP_UPDATE_RESOLUTION, DROP_DELETE_RESOLUTION, DROP_UNIQUE_RESOLUTION so that the column group or priority group is no longer in use before dropping. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23333 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column "%s" is already part of a column group |
| Long Text: | An attempt was made to add a column to a column group when the column was already a member of a column group. |
| Repair Text: | From Oracle doc: Drop the column from its existing column group before trying to add it to another. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23334 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column "%s" does not exist in table or column group |
| Long Text: | The given column is either null, misspelled or is not part of the given table or column group. |
| Repair Text: | From Oracle doc: Use a column that is a member of the table or column group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | priority group %s already exists |
| Long Text: | The priority group was already registered in the object group. |
| Repair Text: | From Oracle doc: Use a column group name not yet registered in the object group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23336 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | priority group %s does not exist |
| Long Text: | The priority group was already registered in the object group. |
| Repair Text: | From Oracle doc: Use a priority group name not yet registered in the object group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23337 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | priority or value not in priority group %s |
| Long Text: | The specified value or priority has not been registered as part of the priority group. |
| Repair Text: | From Oracle doc: Either specify a different value or priority that is already part of the priority group, or add the value to the priority group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23338 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | priority or value already in priority group %s |
| Long Text: | The specified value or priority has already been registered as part of the priority group. |
| Repair Text: | From Oracle doc: Either specify a different value or priority that not already part of the priority group, or drop the value to the priority group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23339 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate conflict resolution information |
| Long Text: | The specified combination of column group, sequence, conflict type and/or parameter table name, parameter column name, and parameter sequence number has already been registered. |
| Repair Text: | From Oracle doc: Verify that additional conflict resolution information needs to be added and provide a new sequence number. If modifying existing information, the existing information must be dropped first. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect resolution method %s |
| Long Text: | User function is specified when conflict resolution method was not "USER FUNCTION" or specified resolution method is not one of the predefined methods. |
| Repair Text: | From Oracle doc: If user function is specified when conflict resolution method was not "USER FUNCTION", either reregister function with method as "USER FUNCTION" or specify a NULL user function. Otherwise, specify one of the documented supported conflict resolution methods. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user function required |
| Long Text: | A NULL user function was specified for the "USER FUNCTION" method. |
| Repair Text: | From Oracle doc: Provide user function name (for example, "schema"."package"."function") that conforms to the documented user function specifications or specify one of the documented supported conflict resolution methods. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid parameter column "%s" |
| Long Text: | The parameter column name is null or misspelled, the invocation database is not a master, or is of the wrong type for the specified conflict resolution method. |
| Repair Text: | From Oracle doc: Specify a parameter column from the specified column group that has a correct type for the conflict resolution method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23343 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no match for specified conflict resolution information |
| Long Text: | The specified combination of column group, sequence, conflict type has not been registered (for example, for adding a comment). |
| Repair Text: | From Oracle doc: Specify a combination of column group, sequence, conflict type has been registered. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | constraint (%s.%s) does not exist |
| Long Text: | A null, misspelled or non-existent constraint was specified when registering a uniqueness conflict. |
| Repair Text: | From Oracle doc: Register a named constraint for the specified table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table "%s"."%s" not registered to collect statistics |
| Long Text: | A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics. |
| Repair Text: | From Oracle doc: Call DBMS_REPCAT.REGISTER_STATISTICS to register the table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23346 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | primary key is undefined for table or snapshot %s |
| Long Text: | An attempt was made to generate replication support for a table or snapshot without a primary key as defined by a constraint or DBMS_REPCAT.SET_COLUMNS. |
| Repair Text: | From Oracle doc: For a table, add a primary key constraint or define a primary key using DBMS_REPCAT.SET_COLUMNS. For a ROWID snapshot, set MIN_COMMUNICATION to false or use a primary key snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23347 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datatype %s for column "%s" table %s not supported |
| Long Text: | The table has a column whose datatype is not supported by REPCAT. |
| Repair Text: | From Oracle doc: Remove the column from the table, or alter the column to have one of the supported datatypes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23348 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot replicate procedure %s; only IN parameters supported |
| Long Text: | An attempt was made to generate replication support for a package that has a procedure with OUT or IN OUT parameters. |
| Repair Text: | From Oracle doc: Remove the procedure from the package, or remove the OUT or IN OUT parameters from the procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23349 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot generate replication support for functions |
| Long Text: | An attempt was made to generate replication support for a package that has a public function, or for a standalone function. |
| Repair Text: | From Oracle doc: Remove the public function from the package, or alter the function to be a procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of recursive calls exceeded |
| Long Text: | This usually occurs when trying to resolve conflicts in a table while concurrent updates to the same row create more conflicts. |
| Repair Text: | From Oracle doc: Re-execute the deferred transaction from DefError using DBMS_DEFER_SYS.EXECUTE_ERROR. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter datatype %s for procedure %s not supported |
| Long Text: | The procedure has a parameter whose datatype is not supported by REPCAT. |
| Repair Text: | From Oracle doc: Remove the parameter from the procedure, or alter the parameter to have one of the supported datatypes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate destination for deferred transaction |
| Long Text: | A duplicate destination was specified for a deferred transaction either in a DBMS_DEFER.CALL call or an earlier DBMS_DEFER.TRANSACTION call or a dbms_defer_sys.add_default_dest call. |
| Repair Text: | From Oracle doc: Remove the duplicate entry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | deferred RPC queue has entries for object group %s.%s |
| Long Text: | The requested action cannot be performed until the queue is empty for the given object group. |
| Repair Text: | From Oracle doc: Use DBMS_DEFER_SYS.EXECUTE or DBMS_DEFER_SYS.DELETE_TRAN to empty the queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | deferred RPC execution disabled for "%s" |
| Long Text: | Deferred RPC cannot be executed at the destination because their propagation has been disabled. |
| Repair Text: | From Oracle doc: Enable deferred RPC execution with the DBMS_DEFER_SYS.ENABLE call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23355 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s.%s does not exist or is invalid at master site |
| Long Text: | The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object at the master site, or the object does not exist as a replicated object with the appropriate status. |
| Repair Text: | From Oracle doc: Ensure the object is valid in the master database, and is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23356 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | masterdef recognizes a master which does not recognize the masterdef |
| Long Text: | Possibly DROP_MASTER_REPGROUP was run at a master site but REMOVE_MASTER_DATABASES was not run at master definition site for that master. |
| Repair Text: | From Oracle doc: Run REMOVE_MASTER_DATABASES from master definition site to remove the appropriate master (see associated error messages). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23357 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the propagator does not exist |
| Long Text: | The propagator does not exist. |
| Repair Text: | From Oracle doc: Register a new propagator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23358 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid remote user |
| Long Text: | The local user does not match the remote user connected via a database link. |
| Repair Text: | From Oracle doc: Drop and re-create the identified database link with the connect-to user identical to the owner of the database link. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23359 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error on creating a ddl record for a repcatlog record |
| Long Text: | The USERID in the REPCATLOG record does not match the USERID of the connected user. |
| Repair Text: | From Oracle doc: Retry the operation with a different user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one snapshot for master table "%s" can be created |
| Long Text: | An attempt was made to create more than one snapshot on a given master table in the same rep group. |
| Repair Text: | From Oracle doc: Create these other snapshots in a different rep group at another site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s" does not exist at master site |
| Long Text: | The snapshot does not exist at the master site for offline instantiation of the snapshot. |
| Repair Text: | From Oracle doc: The correct procedure is to create the snapshot in a different schema at the master site, and then follow the instructions for offline instantiation of snapshots. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid user |
| Long Text: | The given user does not exist. |
| Repair Text: | From Oracle doc: Enter the name of a valid user and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | mismatch of snap base table "%s" at master and snap site |
| Long Text: | The name of the base table of the snapshot at the master site is different from the base table at the snapshot site. This error may arise during offline instantiation of snapshots. |
| Repair Text: | From Oracle doc: Retry offline instantiation with a snapshot name less than 24 bytes |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23364 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Feature not enabled: Advanced replication |
| Long Text: | The Advanced Replication feature is not enabled at this site. Updatable snapshots, deferred RPCs, and other replication features are, therefore, unavailable. |
| Repair Text: | From Oracle doc: Do not attempt to use this feature. Contact Oracle Customer Support if the Advanced Replication feature has been purchased but not enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23365 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | site %s does not exist |
| Long Text: | site specified in argument REFERENCE_SITE or argument COMPARISON_SITE in call to DIFFERENCES() routine or RECTIFY() routine does not name an existing site. |
| Repair Text: | From Oracle doc: Make sure that database sites specified really do exist, and rerun the routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23366 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | integer value %s is less than 1 |
| Long Text: | Value of argument MAX_MISSING to routine DIFFERENCES() cannot be less than 1. Value of argument COMMIT_ROWS to routines DIFFERENCES() and RECTIFY() cannot be less than 1. |
| Repair Text: | From Oracle doc: Choose an integer value for those arguments to be 1 or greater. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23367 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table %s is missing the primary key |
| Long Text: | Table specified in argument "oname1" or "oname2" in call to "differences()" routine does not contain either a primary key or a virtual primary key (defined through DBMS_REPCAT package under symmetric replication). |
| Repair Text: | From Oracle doc: Make sure the tables specified have a primary key defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23368 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name %s cannot be null or the empty %s |
| Long Text: | Argument SNAME1, SNAME2, ONAME1, ONAME2, MISSING_ROWS_SNAME, MISSING_ROWS_ONAME1, MISSING_ROWS_ONAME2 to DIFFERENCES() or RECTIFY() cannot be NULL or '' (empty string). |
| Repair Text: | From Oracle doc: Change argument to non-null or non-empty string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value of "%s" argument cannot be null |
| Long Text: | Argument MAX_MISSING to DIFFERENCES() routine cannot be NULL. |
| Repair Text: | From Oracle doc: Legal values for MAX_MISSING are integers 1 or greater. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23370 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table %s and table %s are not shape equivalent (%s) |
| Long Text: | The tables specified are not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths are not the same. Specifically, problem is in the parentheses and is one of the following: the number of columns are not equal, datatypes of columns with same name in different tables are different, lengths of varchar2 and char columns are not equal, precision and scale of number datatypes are not equal. |
| Repair Text: | From Oracle doc: Make sure the two tables being compared have the same number of columns, same column names, and same datatypes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23371 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column %s unknown in table %s |
| Long Text: | Some column in ARRAY_COLUMNS argument (or COLUMN_LIST argument) to DIFFERENCES() routine does not correspond to a column in the specified table. |
| Repair Text: | From Oracle doc: Make sure that all the columns in either ARRAY_COLUMNS or COLUMN_LIST are present in the specified table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23372 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | type %s in table %s is unsupported |
| Long Text: | Certain types in the table comparison utility are not supported. |
| Repair Text: | From Oracle doc: Make sure that the types of columns in the tables to be compared are the ones supported by symmetric replication. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23373 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object group %s.%s does not exist |
| Long Text: | The group name was null or misspelled, or the group does not exist locally. |
| Repair Text: | From Oracle doc: Specify the group correctly, or create it with DBMS_REPCAT.CREATE_MASTER_REPGROUP(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23374 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object group %s.%s already exists |
| Long Text: | The given database already replicates the given object group. A snapshot repgroup cannot be created at a given site where a master repgroup with the same name already exists. |
| Repair Text: | From Oracle doc: Choose a different group or a different database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23375 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | feature is incompatible with database version at %s |
| Long Text: | A feature not compatible with the specified database was used. |
| Repair Text: | From Oracle doc: Set or raise the value of the COMPATIBLE initialization parameter to match the necessary compatibility level. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23376 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | node %s is not compatible with replication version "%s" |
| Long Text: | A feature not compatible with the remote database was used. |
| Repair Text: | From Oracle doc: Upgrade the remote database and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23377 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad name %s for missing_rows_oname1 argument |
| Long Text: | An attempt was made to use the name of the reference site table as the name of the missing_rows_oname1 argument. |
| Repair Text: | From Oracle doc: Provide a separately created table with a different name for MISSING_ROWS_ONAME1 argument. The separately created table will contain the differences between the tables being compared. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23378 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection qualifier "%s" is not valid for object group %s.%s |
| Long Text: | The connection qualifier used in the database link for the specified object group does not match the qualifier specified for the group in CREATE_MASTER_REPGROUP. |
| Repair Text: | From Oracle doc: Use or create a database link which contains the correct connection qualifier. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23379 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection qualifier "%s" is too long |
| Long Text: | The maximum length of a database link, including the connection qualifier, is 128 bytes. |
| Repair Text: | From Oracle doc: Use a shorter connection qualifier, or shorten the name of the database link |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23380 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | propagation mode "%s" is not valid |
| Long Text: | The specified propagation is misspelled, or is not supported. For snapshot sites, all snapshot object groups at the same snapshot site with the same master object group must all have the same propagation method. |
| Repair Text: | From Oracle doc: Refer to Oracle8i Replication for valid propagation modes. For snapshot sites, also ensure that the propagation modes of all snapshot object groups with the same master object group are the same. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23381 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | generated object for base object %s.%s@%s does not exist |
| Long Text: | The system generated object(s) for the specified base object do not exist at the specified site. The current operation requires the base object to have generated replication support. |
| Repair Text: | From Oracle doc: Ensure that the generated replication object(s) for the base object exist and are valid at the specified site. If the generated object(s) do not exist, then the procedure DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() needs to be called from the master definition site for the base object. missing_rows_oname1 argument. The separately created table will contain the differences between the tables being compared. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23382 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | snapshot repgroup %s.%s is not registered at site %s |
| Long Text: | The snapshot REPGROUP is not currently registered at the master and so cannot be unregistered. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23383 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | registration for snapshot repgroup %s.%s failed at site %s |
| Long Text: | Insertion into local REPSCHEMA table failed. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23384 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication parallel push %s argument out of range |
| Long Text: | Specified numeric argument to DBMS_DEFER_SYS.PUSH is invalid. |
| Repair Text: | From Oracle doc: Fix the argument value and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23385 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication parallel push %s argument not valid |
| Long Text: | Specified string argument to DBMS_DEFER_SYS.PUSH is invalid. |
| Repair Text: | From Oracle doc: Fix the argument value and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23386 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication parallel push cannot create slave processes |
| Long Text: | An error was occurred while creating slave processes for parallel push. |
| Repair Text: | From Oracle doc: If the PARALLEL_MAX_SERVERS initialization parameter is zero, reconfigure the parameter to be greater than zero. Otherwise, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23387 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication parallel push dequeue error |
| Long Text: | An attempt to dequeue a deferred transaction failed while trying to assign a new queue batch number. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23388 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication parallel push watermark error |
| Long Text: | An error occurred during parallel push while trying to update the high-water-mark information in SYSTEM.DEF$_DESTINATION. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23389 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | obsolete procedure; drop objects and recreate using new master |
| Long Text: | DBMS_REPCAT.SWITCH_SNAPSHOT_MASTER is no longer supported. |
| Repair Text: | From Oracle doc: Drop the objects in the object group and re-create them using the new master. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23392 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not find snapshot to be associated with "%s"."%s" |
| Long Text: | Could not find snapshot associated with a trigger or index that is being pulled from the master site. |
| Repair Text: | From Oracle doc: Ensure that snapshot, master, and master index or trigger is registered as replicated objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23393 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | the user is already the propagator |
| Long Text: | The given user is already the current propagator. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23394 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate propagator |
| Long Text: | More than one valid propagator exists. |
| Repair Text: | From Oracle doc: Unregister any duplicate propagator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23395 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object "%s"."%s" of type "%s" does not exist or is invalid |
| Long Text: | The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status. |
| Repair Text: | From Oracle doc: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23396 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database link "%s" does not exist or has not been scheduled |
| Long Text: | The database link does not exist in the schema of the replication propagator or has not been scheduled. |
| Repair Text: | From Oracle doc: Ensure that the database link exists in the database, is accessible and is scheduled for execution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23397 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | global name "%s" does not match database link name "%s" |
| Long Text: | The database link name at the local node does not match the global name of the database that the link accesses. |
| Repair Text: | From Oracle doc: Ensure that global names is set to true and the link name matches the global name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23398 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user name "%s" at database link "%s" does not match local user name "%s" |
| Long Text: | The user name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Symmetric replication expects the two users to be the same. |
| Repair Text: | From Oracle doc: Ensure that the user ID of the replication administration user at the local node and the user ID at the node corresponding to the database link are the same. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23399 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | generation of replication support for "%s"."%s" is not complete |
| Long Text: | Replication support for the specified object has not been generated or the generation process is not yet complete. |
| Repair Text: | From Oracle doc: Ensure that replication support has been generated for the object. Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate replication support for the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid snapshot name "%s" |
| Long Text: | A null, misspelled, or badly formed snapshot name was given to DBMS_SNAPSHOT.REFRESH. |
| Repair Text: | From Oracle doc: Provide a valid snapshot name to DBMS_SNAPSHOT.REFRESH. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" does not exist |
| Long Text: | A snapshot name was given to DBMS_SNAPSHOT.REFRESH that is not in SYS.SNAP$ or its associated views. |
| Repair Text: | From Oracle doc: Provide a snapshot name that is in SYS.SNAP$, ALL_SNAPSHOTS or USER_SNAPSHOTS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh was aborted because of conflicts caused by deferred txns |
| Long Text: | There are outstanding conflicts logged in the DefError table at the snapshot's master. |
| Repair Text: | From Oracle doc: Resolve the conflicts in the master DefError table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS set to TRUE, which will proceed with the refresh even if there are conflicts in the master's DefError table. Proceeding despite conflicts can result with an updatable snapshot's changes appearing to be temporarily lost (until a refresh succeeds after the conflicts are resolved). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh group "%s"."%s" already exists |
| Long Text: | Making a new refresh group when there is already a group of the same name in SYS.RGROUP$. |
| Repair Text: | From Oracle doc: Choose a different refresh group name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh group "%s"."%s" does not exist |
| Long Text: | A refresh group name was given that is not in SYS.RGROUP$. |
| Repair Text: | From Oracle doc: Provide a refresh group name that is in SYS.RGROUP$ or DBS_RGROUP. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23405 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh group number %s does not exist |
| Long Text: | A refresh group number was given that is not in SYS.RGROUP$. |
| Repair Text: | From Oracle doc: Provide a refresh group number that is in SYS.RGROUP$ or DBS_RGROUP. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges on user "%s" |
| Long Text: | The caller is not the owner of the snapshot and does not have ALTER ANY SNAPSHOT privileges. |
| Repair Text: | From Oracle doc: Perform the operation as the owner of the snapshot or as a user with ALTER ANY SNAPSHOT privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object name %s must be shaped like "schema"."object" or "object" |
| Long Text: | The object name (for example, the rollback segment, the snapshot name, the refresh group) was incorrectly specified. |
| Repair Text: | From Oracle doc: Retry the operation with the object name properly specified (like "schema"."object" or "object"). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this replication operation is not supported in a mixed configuration |
| Long Text: | Operation is not supported if the object group is replicated at a pre-V8 node. |
| Repair Text: | From Oracle doc: Ensure that all nodes of the replicated object group are V8. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23409 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not find an unused refresh group number |
| Long Text: | 1000 consecutive refresh group numbers, as defined by the RGROUPSEQ number, were already used by rows in SYS.RGROUP$. |
| Repair Text: | From Oracle doc: Alter the sequence number to be within a legal unused range and destroy unneeded refresh groups. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23410 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" is already in a refresh group |
| Long Text: | A snapshot of the same name is already in a refresh group. |
| Repair Text: | From Oracle doc: Subtract the snapshot from the current refresh group and add it to its new refresh group, or combine the two refresh groups into a single refresh group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23411 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" is not in refresh group "%s"."%s" |
| Long Text: | The specified snapshot is not in the specified refresh group. |
| Repair Text: | From Oracle doc: Try again with the proper snapshot and refresh group names. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23412 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | master table's primary key columns have changed |
| Long Text: | The master table's primary key constraint was modified after the primary key snapshot was created. |
| Repair Text: | From Oracle doc: Drop and re-create the primary key snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23413 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table "%s"."%s" does not have a snapshot log |
| Long Text: | The fast refresh cannot be performed because the master table does not contain a snapshot log. |
| Repair Text: | From Oracle doc: Use the CREATE SNAPSHOT LOG command to create a snapshot log on the master table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23414 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot log for "%s"."%s" does not record rowid values |
| Long Text: | A ROWID snapshot is being fast refreshed, but the snapshot log does not record ROWID information. |
| Repair Text: | From Oracle doc: Use the CREATE SNAPSHOT LOG...ADD ROWID command to begin recording ROWID information in the snapshot log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23415 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot log for "%s"."%s" does not record the primary key |
| Long Text: | A primary key snapshot is being fast refreshed, but the snapshot log does not record primary key information. |
| Repair Text: | From Oracle doc: Use the CREATE SNAPSHOT LOG...ADD PRIMARY KEY command to begin recording primary key information in the snapshot log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23416 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table "%s"."%s" does not contain a primary key constraint |
| Long Text: | The master table does not contain a primary key constraint or the primary key constraint has been disabled. |
| Repair Text: | From Oracle doc: Create a primary key constraint on the master table or enable the existing constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23417 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown snapshot type: %s |
| Long Text: | A fast refresh is being performed on a snapshot of an unknown or unsupported type. |
| Repair Text: | From Oracle doc: Check ALL_SNAPSHOTS and ensure that the snapshot being refreshed is a valid snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23418 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot unregister the propagator who is currently in use |
| Long Text: | The propagator is currently used in propagating replication RPCs. |
| Repair Text: | From Oracle doc: Try again later when there is no transaction active in propagating replication RPCs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23419 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | regenerate replication support before resuming master activity |
| Long Text: | There are tables in the object group that require regeneration of replication support. |
| Repair Text: | From Oracle doc: Check the GENERATION_STATUS column in the ALL_REPOBJECTS view. Regenerate replication support for any table in the object group with a 'NEEDSGEN' status. Resume master activity. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23420 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | interval must evaluate to a time in the future |
| Long Text: | The parameter INTERVAL evaluates to a time earlier than SYSDATE. |
| Repair Text: | From Oracle doc: Choose an expression that evaluates to a time later than SYSDATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23421 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | job number %s is not a job in the job queue |
| Long Text: | There is no job visible to the caller with the given job number. |
| Repair Text: | From Oracle doc: Choose the number of a job visible to the caller. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23422 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Oracle Server could not generate an unused job number |
| Long Text: | Oracle Server could not generate a job number that was not used to identify another job. |
| Repair Text: | From Oracle doc: Retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23423 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | job number %s is not positive |
| Long Text: | The given job number is less than 1. |
| Repair Text: | From Oracle doc: Choose a positive integer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23424 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" at %s not registered |
| Long Text: | The specified snapshot has not be successfully registered at this site. |
| Repair Text: | From Oracle doc: Register the snapshot manually at either the master site or the snapshot site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23425 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid snapshot identifier %s |
| Long Text: | The argument provided to DBMS_SNAPSHOT.PURGE_SNAPSHOT_FROM_LOG is an invalid snapshot identifier or it does not identify an Oracle 8 fast refreshable snapshot or the snapshot has been already purged. |
| Repair Text: | From Oracle doc: If the snapshot is an Oracle 8 fast refreshable snapshot then provide PURGE_SNAPSHOT_FROM_LOG with its valid snapshot identifier. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23426 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | deferred RPC queue has entries for %s |
| Long Text: | The requested action cannot be performed until the queue is empty for the given site/database link. |
| Repair Text: | From Oracle doc: Use DBMS_DEFER_SYS.PUSH, DBMS_DEFER_SYS.PURGE_QUEUE or DBMS_DEFER_SYS.DELETE_TRAN to empty the queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23427 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | deferred purge queue argument %s out of range |
| Long Text: | Specified numeric argument to DBMS_DEFER_SYS.PURGE_QUEUE is invalid. |
| Repair Text: | From Oracle doc: Fix the argument value and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23428 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | job associated instance number %s is not valid |
| Long Text: | A job is associated with an instance that is not running. |
| Repair Text: | From Oracle doc: Choose a running instance for job affinity, or set force parameter to TRUE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument "%s" cannot be NULL or empty %s |
| Long Text: | The caller has provided an argument whose value cannot be NULL or the empty string. |
| Repair Text: | From Oracle doc: Check that the varchar2 value provided is not NULL or the empty string, and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong state: %s |
| Long Text: | The routine was executed against a replicated object group that was in the wrong state. |
| Repair Text: | From Oracle doc: Make sure that the replicated object group is in the state given in the error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | master site %s already exists |
| Long Text: | An attempt was made to instantiate a replicated object group at a master site that was already a part of the object group. |
| Repair Text: | From Oracle doc: If you were trying to add this site, do nothing because it already exists; otherwise, pick the name of another site, and rerun the routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | executing against wrong master site %s |
| Long Text: | An attempt was made to execute the routine at a site that is different from the site specified in the argument of the routine. |
| Repair Text: | From Oracle doc: Provide an argument to the routine that correctly indicates the site against which the routine should be executing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23434 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | master site %s not known for object group |
| Long Text: | The site name given as an argument to a routine was not already known to the replicated object group. |
| Repair Text: | From Oracle doc: Execute the DBMS_OFFLINE_OG.BEGIN_INSTANTIATION() routine to add a new site to the replicated object group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23435 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create an updatable ROWID snapshot with LOB columns |
| Long Text: | The propagation of LOB data from snapshot sites to the master site requires a primary key on the replicated table. Thus updatable ROWID snapshots that contain LOB columns are not supported. |
| Repair Text: | From Oracle doc: Create a primary key snapshot instead of a ROWID snapshot. If the snapshot already exists, it can be converted to a primary key snapshot using the ALTER SNAPSHOT DDL command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing template authorization for user |
| Long Text: | The specified template authorization does not exist. |
| Repair Text: | From Oracle doc: Check the values for user name, refresh template name or AUTH_TEMPLATE_ID to ensure a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | template authorization already exists for user |
| Long Text: | The specified user already has been authorized to use the specified refresh group template. |
| Repair Text: | From Oracle doc: Check the values for user name and refresh template name or query the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that the correct values were passed as parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing refresh group template |
| Long Text: | The specified refresh group template does not exist. |
| Repair Text: | From Oracle doc: Verify that the refresh group template does not exist by querying the DBA_REPCAT_REFRESH_TEMPLATES view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23439 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh group template already exists |
| Long Text: | The specified refresh group template already exists. |
| Repair Text: | From Oracle doc: Verify that the refresh group template exists by querying the DBA_REPCAT_REFRESH_TEMPLATES view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect public template value |
| Long Text: | The public template parameter is not 'Y', 'N' or NULL. |
| Repair Text: | From Oracle doc: Correct the value of the public template parameter. It must be 'Y','N' or NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object does not exist for refresh group template |
| Long Text: | The specified object does not exist in the refresh group template. |
| Repair Text: | From Oracle doc: Correct the object name and object type parameters. Check the DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct name and type of the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23442 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object already exists for the refresh group template |
| Long Text: | The specified object already exists in the refresh group template. |
| Repair Text: | From Oracle doc: Change the object name and object type parameters. Query the DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct name and type of the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23443 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing template parameter |
| Long Text: | The specified template parameter does not exist. |
| Repair Text: | From Oracle doc: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23444 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate template parameter |
| Long Text: | The template parameter already exists for the specified refresh group template. |
| Repair Text: | From Oracle doc: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23445 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing template site |
| Long Text: | The template site specified by the site name, user name and refresh group template name does not exist. |
| Repair Text: | From Oracle doc: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23446 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate template site |
| Long Text: | The template site specified by the site name, user name and refresh group template name already exists. |
| Repair Text: | From Oracle doc: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23447 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing user parameter value |
| Long Text: | The user parameter value specified by the user name, parameter name and refresh group template name does not exist. |
| Repair Text: | From Oracle doc: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARM_VALUES view to query the existing user parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23448 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate user parameter value |
| Long Text: | The user parameter value specified by the user name, parameter name and refresh group template name already exists. |
| Repair Text: | From Oracle doc: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARM_VALUES view to query the existing user parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23449 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing user name |
| Long Text: | The user specified by the user name parameter does not exist in the database. |
| Repair Text: | From Oracle doc: Correct an invalid user name or create the user in the master database. Use the DBA_USERS view to select the valid database users. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23450 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor already contains object "%s"."%s" |
| Long Text: | The flavor already contains the specified object. |
| Repair Text: | From Oracle doc: Check that the specified object is correct. To add all columns of a table object, delete the object from the flavor and then add it again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor %s already defined for object group %s.%s |
| Long Text: | The given object group already contains a (possibly unpublished) definition of the specified flavor. |
| Repair Text: | From Oracle doc: Check the spelling of the flavor name. Check for an unpublished flavor of the desired name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor %s of object group %s.%s is already published |
| Long Text: | The given object group already contains a (published) definition of the specified flavor. |
| Repair Text: | From Oracle doc: Check the spelling of the flavor name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | requested operation is not supported on top flavor |
| Long Text: | The TOP flavor has a NULL name and may not be directly defined or deleted. |
| Repair Text: | From Oracle doc: Supply the name of a flavor other than the TOP flavor or use DBMS_REPCAT routines to implicitly change the TOP flavor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23454 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor %s not defined for object group %s.%s |
| Long Text: | The given object group does not contain a (published) definition of the specified flavor. |
| Repair Text: | From Oracle doc: Check the spelling of the flavor name. Ensure the flavor has been defined (and published) for the object group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23455 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor %s contains object "%s" |
| Long Text: | The given flavor contains the object to be dropped. |
| Repair Text: | From Oracle doc: Purge the flavor or choose another object to drop. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23456 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor %s does not contain "%s" |
| Long Text: | The flavor does not contain the given object, column, or attribute. |
| Repair Text: | From Oracle doc: Either drop the flavor or choose a different object, column, or attribute. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23457 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid flavor ID %s |
| Long Text: | The given flavor ID is invalid. |
| Repair Text: | From Oracle doc: Make sure this flavor has been instantiated. If the flavor ID is outside the range (-2147483647, 2147483647), contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23458 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inappropriate flavor %s at %s |
| Long Text: | The given flavor at the given database prevents the operation from succeeding. |
| Repair Text: | From Oracle doc: Either change the database flavor or choose a different operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23459 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor %s must contain "%s" |
| Long Text: | The flavor must contain the given object, column, or attribute. |
| Repair Text: | From Oracle doc: Either choose a different database flavor or ensure the object, column, or attribute is available. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23460 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing value for column %s in resolution method "%s" for "%s"."%s"."%s" |
| Long Text: | Before resolving conflicts, some values necessary for resolving conflicts are not available; or, after resolving conflicts, some values necessary for retrying the SQL are not available. |
| Repair Text: | From Oracle doc: define appropriate flavors, provide necessary values through availability vector in USER FLAVOR FUNCTION for conflict resolution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23461 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fail to resolve conflict for "%s"."%s"."%s" |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23462 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor %s in use at site %s |
| Long Text: | The given flavor cannot be deleted because it is being used at the given site. |
| Repair Text: | From Oracle doc: Change the flavor of the site, or unregister it if it is a snapshot site. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23463 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor incompatible with object "%s"."%s" |
| Long Text: | An existing flavor includes the specified object with an incompatible type. |
| Repair Text: | From Oracle doc: Change the type of the object, or delete the flavor if it is not in use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23464 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor lacks column %s of "%s"."%s" |
| Long Text: | The flavor includes some columns of an object group but not all the required columns. |
| Repair Text: | From Oracle doc: Change the flavor definition to include all required columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23465 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor already includes column %s of "%s"."%s" |
| Long Text: | The flavor includes the specified column which is being added. |
| Repair Text: | From Oracle doc: Check that the specified column is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23466 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor requires missing object "%s"."%s" |
| Long Text: | The flavor includes the specified object which does not exist. |
| Repair Text: | From Oracle doc: Check that the specified object name is correct, and create the object if appropriate. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23467 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | flavor lacks object "%s"."%s" |
| Long Text: | The flavor does not include the specified object which is being dropped. |
| Repair Text: | From Oracle doc: Check that the specified object is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23468 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing %s %s |
| Long Text: | The template is missing the object with the specified key. |
| Repair Text: | From Oracle doc: Add the object to the template. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23469 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is different between templates |
| Long Text: | The values for the specified columns are different in each template for the same key values. |
| Repair Text: | From Oracle doc: Correct the column values to make the templates the same. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23470 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid status |
| Long Text: | The status should be DELETED, INSTALLING or INSTALLED. Any other status is invalid. |
| Repair Text: | From Oracle doc: Check that the specified status value is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23471 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | template not authorized for user |
| Long Text: | The refresh template is private and the user has not been authorized to instantiate the template. |
| Repair Text: | From Oracle doc: Authorize the user to use the template. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23472 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot "%s"."%s" must be atomically refreshed |
| Long Text: | Non-atomic refresh is not supported for the specified snapshot. |
| Repair Text: | From Oracle doc: Set the value of the ATOMIC parameter to FALSE in the refresh procedure being used or remove the specified snapshot from the set of snapshots being refreshed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23473 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication RPC processing for "%s"."%s" is disabled |
| Long Text: | The processing of replication RPCs for the object group that contains this object is disabled. This includes RPCs in the error queue. |
| Repair Text: | From Oracle doc: Processing of replication RPCs is disabled when the object group is being offline instantiated. Wait until offline instantiation is finished. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23474 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | definition of "%s"."%s" has changed since generation of replication support |
| Long Text: | The current columns in the specified table and their column types do not match the columns and column types when replication support was last generated. |
| Repair Text: | From Oracle doc: Regenerate replication support for the affected table. All flavors that include the specified table should also be checked for validity. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23475 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | key column "%s" must be sent and compared |
| Long Text: | The specified column is a key column and must be sent and compared during replication propagation. |
| Repair Text: | From Oracle doc: Make sure every key column is sent and compared. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23476 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot import from %s to %s |
| Long Text: | This object was imported from a database with a different global name than the importing database. |
| Repair Text: | From Oracle doc: Only import this object into a database with the same global name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23477 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to alter propagation mode for object group %s.%s |
| Long Text: | The propagation method of a snapshot object group can only be altered when no other object groups with the same master object group are sharing the snapshot site. |
| Repair Text: | From Oracle doc: Ensure that there are no other snapshot object groups at the local site with the same master object group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-23478 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object group %s is already mastered at %s |
| Long Text: | There is at least one other snapshot repgroup at the local site with the same group name but a different master site. |
| Repair Text: | From Oracle doc: Ensure that all snapshot repgroups at the local site with the same group name have the same master. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, %s should be of the form [SCHEMA.]NAME |
| Long Text: | An invalid value was specified for the parameter. |
| Repair Text: | From Oracle doc: Specify a string of the form [SCHEMA.]NAME. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create QUEUE_TABLE, %s already exists |
| Long Text: | The queue table already exists in the queueing system. |
| Repair Text: | From Oracle doc: Drop the table first using the DROP_QUEUE_TABLE() command or specify another table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | QUEUE_TABLE %s does not exist |
| Long Text: | QUEUE_TABLE does not exist. |
| Repair Text: | From Oracle doc: Query on the user view USER_QUEUE_TABLES to find out existing queue tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Queue table index %s inconsistent with queue table %s |
| Long Text: | The queue table index has not yet been successfully imported. |
| Repair Text: | From Oracle doc: Import the queue table index before attempting to use the queue table. If the import failed, correct the problem and try to import the queue table index again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid column name %s in SORT_LIST, should be ENQ_TIME or PRIORITY |
| Long Text: | Invalid column name was specified in the SORT_LIST. |
| Repair Text: | From Oracle doc: The valid column names are ENQ_TIME and PRIORITY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables |
| Long Text: | An attempt was made to use the SQL command DROP TABLE for queue tables, but DROP TABLE is not supported for queue tables. |
| Repair Text: | From Oracle doc: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure instead of the DROP TABLE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create QUEUE, %s already exists |
| Long Text: | The queue requested to be created already exists. |
| Repair Text: | From Oracle doc: Specify another queue name. Query USER_QUEUES for all the existing queues in the users's schema. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, MAX_RETRIES should be non-negative integer |
| Long Text: | An invalid value was specified for MAX_RETRIES. |
| Repair Text: | From Oracle doc: Specify a non-negative integer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | queue table %s.%s must be dropped first |
| Long Text: | An error was detected when dropping a queue table in a cluster, tablespace, or schema. |
| Repair Text: | From Oracle doc: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop the specified queue table first; then, retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE |
| Long Text: | Invalid queue type parameter. |
| Repair Text: | From Oracle doc: Valid values are NORMAL_QUEUE for normal queue and EXCEPTION_QUEUE for exception queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | QUEUE %s does not exist |
| Long Text: | The specified queue does not exist. |
| Repair Text: | From Oracle doc: Specify a valid queue. Query USER_QUEUES for all the valid queues. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop QUEUE, %s should be stopped first |
| Long Text: | The queue has not been stopped. That is, either enqueue or dequeue is still enabled. |
| Repair Text: | From Oracle doc: Stop the queue first using the STOP_QUEUE command and disable it from both enqueueing and dequeueing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop QUEUE_TABLE, some queues in %s have not been dropped |
| Long Text: | A queue exists in the queue table which has not been dropped. All queues need to be dropped first. |
| Repair Text: | From Oracle doc: Drop all queues belonging to this queue table using the DROP_QUEUE() command. Be sure to stop the queues appropriately before dropping them. Alternately, use the force option in DROP_QUEUETABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, RETRY_DELAY should be non-negative |
| Long Text: | A negative value was specified for RETRY_DELAY. |
| Repair Text: | From Oracle doc: Specify a non-negative value for RETRY_DELAY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, RETENTION_TIME should be FOREVER or non-negative |
| Long Text: | Queue retention was specified, but the retention time was specified to be less than zero. |
| Repair Text: | From Oracle doc: Specify the retention time to be non-negative or FOREVER. Alternately do not specify retention. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE %s.%s does not exist |
| Long Text: | An invalid QUEUE_PAYLOAD_TYPE specified during CREATE_QUEUE_TABLE. |
| Repair Text: | From Oracle doc: The QUEUE_PAYLOAD_TYPE should be RAW or an object type that already exists in the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create QUEUE_TABLE, user %s does not have execute privileges on QUEUE_PAYLOAD_TYPE %s.%s |
| Long Text: | An invalid object type specified for QUEUE_PAYLOAD_TYPE during CREATE_QUEUE_TABLE. |
| Repair Text: | From Oracle doc: Make sure you have execute privileges on the object type specified for the queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24017 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot enable enqueue on QUEUE, %s is an exception queue |
| Long Text: | An attempt was made to enable enqueueing to an exception queue. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | STOP_QUEUE on %s failed, outstanding transactions found |
| Long Text: | There were outstanding transactions on the queue, and WAIT was set to false, so STOP_QUEUE was unsuccessful in stopping the queue. |
| Repair Text: | From Oracle doc: Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all outstanding transactions are completed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | identifier for %s too long, should not be greater than %s characters |
| Long Text: | The identifier specified is too long. |
| Repair Text: | From Oracle doc: Try again with a shorter identifier. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Internal error in DBMS_AQ_IMPORT_INTERNAL, %s |
| Long Text: | An internal error occurred in the package. DBMS_AQ_IMPORT_INTERNAL. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | queue table definition not imported for %s.%s |
| Long Text: | The queue definition is not updated because the queue table was not imported properly. |
| Repair Text: | From Oracle doc: Import the queue table again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24022 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | the specified parameters has no effect on the queue |
| Long Text: | The parameter combination will not cause the queue to be started or stopped. |
| Repair Text: | From Oracle doc: No action required. This is a warning. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Internal error in DBMS_AQ_EXP_INTERNAL.%s [%s] [%s] |
| Long Text: | An internal error occurred in the package DBMS_AQ_EXP_INTERNAL. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Internal error in DBMS_AQ_IMP_INTERNAL.%s [%s] [%s] |
| Long Text: | An internal error occurred in the package DBMS_AQ_IMP_INTERNAL. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, QUEUE_PAYLOAD_TYPE should be RAW or an object type |
| Long Text: | Parameter QUEUE_PAYLOAD_TYPE has invalid value. |
| Repair Text: | From Oracle doc: Specify a valid object type or RAW. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value, %s should be non-NULL |
| Long Text: | Parameter is NULL. |
| Repair Text: | From Oracle doc: Specify a non-NULL value for the parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s exists, index could not be created for queue table %s |
| Long Text: | Oracle AQ tried to create an index with the name specified in the error message. The index could not be created for the specified queue table because a object exists with the same name. |
| Repair Text: | From Oracle doc: Drop the object specified in the error message and retry the command. You can also choose a different name for the queue table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24033 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no recipients for message |
| Long Text: | An enqueue was performed on a queue that has been set up for multiple dequeuers but there were neither explicit recipients specified in the call nor were any queue subscribers determined to be recipients for this message. |
| Repair Text: | From Oracle doc: Either pass a list of recipients in the enqueue call or add subscribers to the queue for receiving this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24034 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | application %s is already a subscriber for queue %s |
| Long Text: | An application name that was already a subscriber for the queue was specified in the DBMS_AQ.SUBSCRIBE call. |
| Repair Text: | From Oracle doc: Choose another application name and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | AQ agent %s is not a subscriber for queue %s |
| Long Text: | An AQ agent that was not a subscriber for the queue was specified. |
| Repair Text: | From Oracle doc: Check the name and/or address of the agent and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid SORT_ORDER column %s specified for queue table |
| Long Text: | The CREATE QUEUE TABLE command was issued with MESSAGE_GROUPING set to TRANSACTIONAL and a sort order column other than priority. Only the priority column can be specified in the sort order for queue tables with transactional grouping. |
| Repair Text: | From Oracle doc: Change the sort order list in the CREATE QUEUE TABLE command and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | schema %s in QUEUE_NAME is not same as schema %s in QUEUE_TABLE |
| Long Text: | The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE is not the same as the schema specified in the QUEUE_TABLE parameter. |
| Repair Text: | From Oracle doc: Use the same schema name for both the QUEUE_NAME and QUEUE_TABLE parameters and retry the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue |
| Long Text: | The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and a QUEUE_TABLE that was created for multiple consumers and with COMPATIBLE parameter set to '8.0'. |
| Repair Text: | From Oracle doc: Either set the RETRY_DELAY to zero or upgrade the queue table to 8.1 compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Queue %s not created in queue table for multiple consumers |
| Long Text: | Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure, or an ENQUEUE with a non-empty recipient list, was issued on a queue that was not created for multiple consumers. |
| Repair Text: | From Oracle doc: Create the queue in a queue table that was created for multiple consumers and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | propagation schedule exists for QUEUE %s and DESTINATION %s |
| Long Text: | A SCHEDULE_PROPAGATION was issued for a queue and destination pair which has an existing propagation schedule. |
| Repair Text: | From Oracle doc: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule and then reissue the SCHEDULE_PROPAGATION call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no propagation schedule exists for QUEUE %s and DESTINATION %s |
| Long Text: | AN UNSCHEDULE_PROPAGATION was issued for a queue and destination pair which has no existing propagation schedule. |
| Repair Text: | From Oracle doc: Verify the spelling of the specified QUEUE and DESTINATION and then reissue the call with the correct spelling. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | destination %s uses a reserved name, names with AQ$_ prefix are not valid |
| Long Text: | An attempt was made to specify a reserved name for a destination. |
| Repair Text: | From Oracle doc: Enter a different value or NULL for the local destination. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | source %s and destination %s object types do not match |
| Long Text: | A message recipient's queue has a different object structure than the sender's queue. The message cannot be propagated. |
| Repair Text: | From Oracle doc: Either remove the recipient from the subscriber's list for the sender's queue or create the destination queue with an object type that matches the source queue's object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid agent address %s, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK] |
| Long Text: | An invalid value was specified for the agent address parameter. |
| Repair Text: | From Oracle doc: Specify a string of the form [SCHEMA.]NAME[@DATABASE LINK]. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24046 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | protocol attribute reserved for future use |
| Long Text: | The protocol attribute of the AQ agent object type is reserved for future use. |
| Repair Text: | From Oracle doc: Do not specify the protocol attribute in the agent object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24047 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid agent name %s, agent name should be of the form NAME |
| Long Text: | An invalid value was specified for the agent name parameter. |
| Repair Text: | From Oracle doc: Specify a string of the form NAME. Then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24048 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create QUEUE_TABLE, user does not have access to AQ object types |
| Long Text: | An attempt was made to issue the CREATE_QUEUE_TABLE command, but the user who issued the command does not have access to internal AQ object types. |
| Repair Text: | From Oracle doc: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the user access to the AQ object types. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24049 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid agent name %s, names with AQ$_ prefix are not valid |
| Long Text: | An attempt was made to use a reserved prefix in the agent name. |
| Repair Text: | From Oracle doc: Enter a different value for the agent name. Then, retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24050 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subscribers are not supported for exception queue %s |
| Long Text: | An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure was issued on a queue that was created as an EXCEPTION_QUEUE. |
| Repair Text: | From Oracle doc: Specify a NORMAL_QUEUE in the procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24051 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot propagate object type payloads that have a REF or BFILE attribute |
| Long Text: | An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address field in the agent type was issued on a queue whose payload has a REF or BFILE attribute. Propagation of object type payloads that have a REF or BFILE attribute currently is not supported. |
| Repair Text: | From Oracle doc: Specify an agent with a NULL address field so that the agent can dequeue from the same queue. Or, change the object type definition to one that does not use REF or BFILE attributes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot propagate object type payloads with LOB attributes to an 8.0 release |
| Long Text: | The recipient of a message with LOB attributes was using an Oracle 8.0 release. Propagation of LOB attributes is supported only in Oracle 8.1 and higher releases. |
| Repair Text: | From Oracle doc: Upgrade the target release to Oracle 8.1 and retry. Or, change the object type definition to one that does not use LOBs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative |
| Long Text: | One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative. |
| Repair Text: | From Oracle doc: Specify non-negative integers for PRIMARY_INSTANCE and SECONDARY_INSTANCE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24054 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot propagate to an Oracle 8.0.3 release or lower release |
| Long Text: | The recipient of a message was using an Oracle 8.0.3 release or lower release. Propagation is supported only in Oracle 8.0.4 and higher releases. |
| Repair Text: | From Oracle doc: Upgrade the target release to Oracle 8.0.4 or higher and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24055 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot delete propagation status rows that are in prepared state |
| Long Text: | An attempt was made to use the internal administration procedure to delete status rows from the SYS.AQ$_PROPAGATION_STATUS table that were in the prepared state. |
| Repair Text: | From Oracle doc: Wait for the propagation to complete successfully before retrying the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24056 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal inconsistency for QUEUE %s and destination %s |
| Long Text: | The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table were inconsistent for the given queue and destination. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24057 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot define subscriber with rule for queue %s |
| Long Text: | An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was issued on a queue for which rule based subscribers are not supported. Rule based subscribers currently are supported only for NORMAL (persistent) multi-consumer queues created using an Oracle release 8.1.0 or higher compatible queue table. |
| Repair Text: | From Oracle doc: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0 or higher compatible queue table, and retry the call. Or, if the queue is a normal (persistent) multi-consumer queue, convert the queue table to Oracle 8.1.0 or higher compatibility and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24058 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot downgrade QUEUE_TABLE that has propagation in a prepared state |
| Long Text: | An attempt was made to downgrade the queue table when there were messages being propagated that were in the prepared state. |
| Repair Text: | From Oracle doc: Wait for the propagation to complete before retrying the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24059 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid COMPATIBLE parameter setting %s specified in DBMS_AQADM.%s |
| Long Text: | An invalid compatible parameter was specified in the DBMS_AQADM procedure. The parameter setting must be of the form '8.x.y' where x is the release number and y is the update number. |
| Repair Text: | From Oracle doc: Specify a valid COMPATIBLE parameter setting, and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot convert QUEUE_TABLE, %s already is compatible with release %s |
| Long Text: | The source queue table in the DBMS_AQADM procedure is compatible with the specified COMPATIBLE parameter setting. |
| Repair Text: | From Oracle doc: Choose a different COMPATIBLE parameter setting to convert the queue table to the desired compatibility. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero |
| Long Text: | A non-zero value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was zero. |
| Repair Text: | From Oracle doc: Specify a non-zero primary instance before you specify a non-zero secondary instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24062 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Subscriber table %s inconsistent with queue table %s |
| Long Text: | The subscriber table has not yet been successfully imported. |
| Repair Text: | From Oracle doc: Import the subscriber table before attempting to use the queue table. If the import failed, correct the problem and try to import the subscriber table again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24063 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers |
| Long Text: | An attempt was made to downgrade the queue table when there were queues on which rule-based subscribers are defined. |
| Repair Text: | From Oracle doc: Remove the rule-based subscribers for all queues in this queue table and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24064 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | propagation for QUEUE %s and DESTINATION %s already enabled |
| Long Text: | An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was enabled. |
| Repair Text: | From Oracle doc: Make sure the QUEUE and DESTINATION are correct when you issue the ENABLE_SCHEDULE_PROPAGATION command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24065 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | propagation for QUEUE %s and DESTINATION %s already disabled |
| Long Text: | A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was disabled. |
| Repair Text: | From Oracle doc: Make sure the QUEUE and DESTINATION are correct when you issue the DISABLE_SCHEDULE_PROPAGATION command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24066 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid privilege specified |
| Long Text: | An invalid privilege is specified for granting or revoking privilege. |
| Repair Text: | From Oracle doc: Specify a valid privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24067 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded maximum number of subscribers for queue %s |
| Long Text: | An attempt was made to add new subscribers to the specified, but the number of subscribers for this queue has exceeded the maximum number (1024) of subscribers allowed per queue. |
| Repair Text: | From Oracle doc: Remove existing subscribers before trying to add new subscribers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24068 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start queue %s, queue table %s is being migrated |
| Long Text: | An attempt was made to start a queue in a queue table that is being migrated. |
| Repair Text: | From Oracle doc: Complete the queue table migration, and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24069 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot downgrade queue table %s while it is being upgraded |
| Long Text: | An attempt was made to downgrade a queue table, but a previous command to upgrade the queue table has not yet completed successfully. |
| Repair Text: | From Oracle doc: Complete the upgrade of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, downgrade the queue table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24070 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot upgrade queue table %s while it is being downgraded |
| Long Text: | An attempt was made to upgrade a queue table, but a previous command to downgrade the queue table has not yet completed successfully. |
| Repair Text: | From Oracle doc: Complete the downgrade of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, upgrade the queue table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform operation %s, queue table %s is being migrated |
| Long Text: | An attempt was made to perform an operation on a queue in a queue table that is being migrated. |
| Repair Text: | From Oracle doc: Complete the queue table migration, and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24072 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table |
| Long Text: | An attempt was made to upgrade or downgrade a queue table using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the user who executed the procedure does not own the queue. |
| Repair Text: | From Oracle doc: Reconnect as the owner of the queue table, and then execute the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24073 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify RETENTION_TIME on exception queue %s.%s |
| Long Text: | An attempt was made to create or alter an exception queue by specifying a non-zero RETENTION_TIME. |
| Repair Text: | From Oracle doc: Use the default RETENTION_TIME parameter value for exception queues. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RETRY_DELAY and MAX_RETRIES cannot be used for exception queue %s |
| Long Text: | The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and an exception queue. |
| Repair Text: | From Oracle doc: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24075 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify agent with NULL address and non-NULL protocol |
| Long Text: | An ADD_SUBSCRIBER or enqueue was attempted with an agent that had a NULL address and a non-NULL protocol. |
| Repair Text: | From Oracle doc: Either specify a non-NULL address or set the protocol to NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24076 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform operation %s for NON_PERSISTENT queue %s.%s |
| Long Text: | One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN, DEQUEUE was issued for a NON_PERSISTENT queue. |
| Repair Text: | From Oracle doc: Do not specify a NON_PERSISTENT queue for these operations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24077 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create propagation schedule for EXCEPTION queue %s.%s |
| Long Text: | A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. Propagation schedules can be created only for NORMAL queues. |
| Repair Text: | From Oracle doc: To propagate messages from a queue, specify the queue type as NORMAL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL |
| Long Text: | A non-NULL value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was NULL. |
| Repair Text: | From Oracle doc: Specify a non-NULL primary instance before you specify a non-NULL secondary instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24079 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid name %s, names with AQ$_ prefix are not valid for %s |
| Long Text: | An attempt was made to use a reserved prefix for the object name. |
| Repair Text: | From Oracle doc: Enter a different name for this object. Then, retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24080 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unschedule_propagation pending for QUEUE %s and DESTINATION %s |
| Long Text: | A propagation administration command was issued for a queue and destination pair whose propagation is being unscheduled. |
| Repair Text: | From Oracle doc: Do not issue propagation administration commands for a propagation schedule on which there is a pending unschedule request. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24081 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | compatible parameter needs to be %s or greater |
| Long Text: | The value of the COMPATIBLE parameter was not high enough to allow the operation. |
| Repair Text: | From Oracle doc: Shut down and restart with a higher compatibility setting. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | propagation may still be happening for the schedule for QUEUE %s and DESTINATION %s |
| Long Text: | The snapshot process executing the propagation schedule did not respond to the disable propagation command. |
| Repair Text: | From Oracle doc: Make sure that the job for the propagation schedule has been ended. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24083 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify remote subscribers for %s QUEUE %s |
| Long Text: | An ADD_SUBSCRIBER call with a non-null address field was issued on a queue which does not support remote subscribers. Remote subscribers are not supported for NON_PERSISTENT QUEUES. |
| Repair Text: | From Oracle doc: Specify a null address field and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DBLINK name in address field of agent %s is not unique within the first 24 bytes" |
| Long Text: | Advanced Queuing requires that the agent's DBLINK name should be unique within the first 24 bytes (for 8.0 compatible queue tables) |
| Repair Text: | From Oracle doc: Specify a DBLINK name that is unique within the first 24 bytes or migrate to 8.1 compatible queue tables where this restriction is not there. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in ktz testing layer |
| Long Text: | There is an error in the Transaction layer test ICDs. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid %s parameter passed to DBMS_REPAIR.%s procedure |
| Long Text: | An invalid parameter was passed to the specified DBMS_REPAIR procedure. |
| Repair Text: | From Oracle doc: Specify a valid parameter value or use the parameter's default. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure |
| Long Text: | Both cascade and a block range were specified in a call to DBMS_REPAIR.CHECK_OBJECT. |
| Repair Text: | From Oracle doc: Use either cascade or a block range, or do not use either one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid block range specification |
| Long Text: | An incorrect block range was specified. |
| Repair Text: | From Oracle doc: Specify correct values for the BLOCK_START and BLOCK_END parameters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | feature %s is not yet implemented |
| Long Text: | An attempt was made to use the specified feature, but the feature is not yet implemented. |
| Repair Text: | From Oracle doc: Do not attempt to use the feature. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ACTION parameter passed to DBMS_REPAIR.%s procedure |
| Long Text: | An invalid ACTION parameter was specified. |
| Repair Text: | From Oracle doc: Specify CREATE_ACTION, PURGE_ACTION or DROP_ACTION for the ACTION parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Object %s.%s has changed |
| Long Text: | An attempt was made to fix corrupt blocks on an object that has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was run. |
| Repair Text: | From Oracle doc: Use DBMS_REPAIR.ADMIN_TABLES to purge the repair table and run DBMS_REPAIR.CHECK_OBJECT to determine whether there are any corrupt blocks to be fixed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CASCADE_FLAG passed to DBMS_REPAIR.%s procedure |
| Long Text: | CASCADE_FLAG was specified for an object that is not a table. |
| Repair Text: | From Oracle doc: Use CASCADE_FLAG only for tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TABLESPACE parameter specified with an ACTION other than CREATE_ACTION |
| Long Text: | The TABLESPACE parameter can only be used with CREATE_ACTION. |
| Repair Text: | From Oracle doc: Do not specify TABLESPACE when performing actions other than CREATE_ACTION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition name specified for a non-partitioned object |
| Long Text: | A partition name was specified for an object that is not partitioned. |
| Repair Text: | From Oracle doc: Specify a partition name only if the object is partitioned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24129 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table name %s does not start with %s prefix |
| Long Text: | An attempt was made to pass a table name parameter without the specified prefix. |
| Repair Text: | From Oracle doc: Pass a valid table name parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24130 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table %s does not exist |
| Long Text: | An attempt was made to specify a map, repair, or sync table that does not exist. |
| Repair Text: | From Oracle doc: Specify a valid table name parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24131 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table %s has incorrect columns |
| Long Text: | An attempt was made to specify a map, repair, or sync table that does not have a correct definition. |
| Repair Text: | From Oracle doc: Specify a table name that refers to a properly created table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24132 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table name %s is too long |
| Long Text: | An attempt was made to specify a table name is greater than 30 characters long. |
| Repair Text: | From Oracle doc: Specify a valid table name parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24141 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ruleset specified does not exist |
| Long Text: | An attempt to access or modify a ruleset was made, which failed because the ruleset does not exist. |
| Repair Text: | From Oracle doc: Only access or modify existing rulesets. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24142 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid ruleset name |
| Long Text: | An attempt to create a ruleset with an invalid name was made. The ruleset name cannot be NULL, and cannot be more than 26 characters, unless a RULES_TABLE_NAME is also specified, in which case the ruleset name may be up to 30 characters. |
| Repair Text: | From Oracle doc: Retry the create with a valid ruleset name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24143 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid table name |
| Long Text: | An attempt to create a ruleset on an invalid table name was made. The DATA_TABLE name cannot be NULL, and cannot be more than 30 characters. The table with the name specified must exist. |
| Repair Text: | From Oracle doc: Retry the create with a valid table name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24144 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rules engine internal error, arguments: [%s], [%s] |
| Long Text: | An internal error occurred in the rules engine. This indicates that the rules engine has encountered an exception condition. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. The first argument is the error and the second argument is the package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24270 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a row already exists in the %s table for these parameters |
| Long Text: | A call was made to create a new row in the specified table. A row already exists in the table with the specified values. |
| Repair Text: | From Oracle doc: Delete the existing row using the appropriate API or check the parameters used to create the row. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24271 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | translation type must be either T, S or M |
| Long Text: | The translation type parameter is not a T, S or an M. A value other than T, S or M was specified. |
| Repair Text: | From Oracle doc: Correct the translation type and re-execute the API call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24272 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | initialization value must be either F or T |
| Long Text: | The initialization value must be either F or T. A value other than F or T was specified. |
| Repair Text: | From Oracle doc: Correct the initialization value and re-execute the API call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24273 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | translation text is required if translation type is T or S |
| Long Text: | If a translation type of T or S is specified, translation text must be supplied. |
| Repair Text: | From Oracle doc: Provide translation text and re-execute the API call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24274 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no row exists in the %s table for these parameters |
| Long Text: | A call was made to update a row that does not exist or a foreign key value supplied to create a table does not exist. |
| Repair Text: | From Oracle doc: Create the row using the appropriate API or check the parameters used to create the new row to ensure that all specified values exist. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24275 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function '%s' parameter '%s' missing or invalid |
| Long Text: | The function pkgname.funcname was called with a parameter parmname that was null, 0 length, or had an invalid value. |
| Repair Text: | From Oracle doc: Correct the parameter to supply values that comply with its datatype and limits as specified in the documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function '%s' output '%s' maximum value exceeded |
| Long Text: | The function pkgname.funcname computed a value for the output parmname that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype. |
| Repair Text: | From Oracle doc: Correct the input values to produce a result that will comply with the limits as specified in the documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to execute %s |
| Long Text: | The access to the named procedure is limited to users with certain privileges, which the invoker does not have. |
| Repair Text: | From Oracle doc: Check your documentation to verify the privileges needed to execute the named procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | privilege type mismatch |
| Long Text: | Privileges can be granted to a user on an object like execute rights or just to a user like create library rights. Those are different types of privileges. One cannot insert an object privilege into the user privileges table and vice versa. |
| Repair Text: | From Oracle doc: Make sure the privilege type is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24279 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to create library |
| Long Text: | The user tried to create a remote library without having the remote create library privilege. |
| Repair Text: | From Oracle doc: A local database administrator must grant the remote user the create library privilege by invoking DBMS_HS_EXTPROC.GRANT_CREATE_LIBRARY(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24280 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid input value for parameter %s |
| Long Text: | The parameter has been provided a negative, out of range, or NULL input value. |
| Repair Text: | From Oracle doc: Correct the input value such that it is valid, and is within the range as specified in the documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24281 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid access past the maximum size of LOB parameter %s |
| Long Text: | The value of positional or size parameters exceeds the maximum allowed LOB size of 4 Gigabytes. |
| Repair Text: | From Oracle doc: Correct the input values for amount and offset such that their sum is less than or equal to 4 Gigabytes. If error occurs in a read or write loop, check the looping conditions and/or offset increments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad value for mode |
| Long Text: | An undefined mode value was specified. |
| Repair Text: | From Oracle doc: Check that the correct mode is selected and that an allowed value for that mode is specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null host specified in thread-safe logon |
| Long Text: | An HDA was not specified in the logon call while running in a thread safe environment. |
| Repair Text: | From Oracle doc: Make sure that HDA is not NULL when calling the logon routine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24302 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | host connection in use by another thread |
| Long Text: | An attempt was made to use the host connection while it was in use by another thread. |
| Repair Text: | From Oracle doc: Wait for another thread to finish before using this connection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | call not supported in non-deferred linkage |
| Long Text: | One of the calls that is supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred. |
| Repair Text: | From Oracle doc: Use this call in deferred mode of linkage. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datatype not allowed for this call |
| Long Text: | Data of this datatype cannot be sent or fetched in pieces. |
| Repair Text: | From Oracle doc: Use other bind or define calls for this datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad bind or define context |
| Long Text: | The call was executed on a cursor for which this is invalid. |
| Repair Text: | From Oracle doc: Verify that this call is valid for this cursor. For example, Get piece information and set piece information are valid on a cursor if appropriate binds and defines have been done on this cursor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad buffer for piece |
| Long Text: | A zero length buffer or a null buffer pointer was provided. |
| Repair Text: | From Oracle doc: Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24307 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid length for piece |
| Long Text: | The length of the piece exceeded the maximum possible size. |
| Repair Text: | From Oracle doc: Verify that the length of this piece and the cumulative length of all the previous pieces is not more than the desired value supplied by the application. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24308 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal define position |
| Long Text: | Call to modify attributes was done for a non-existent position. |
| Repair Text: | From Oracle doc: Verify that a define has been done for this position. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | already connected to a server |
| Long Text: | This server handle is already attached to a server. |
| Repair Text: | From Oracle doc: Disconnect from the server and then retry the call to establish a connection. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | length specified for null connect %s |
| Long Text: | The connect string is null, but a length was specified for it. |
| Repair Text: | From Oracle doc: Set length to zero if connect string is null. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | memory initialization failed |
| Long Text: | Cannot initialize user memory. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24312 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal parameters specified for allocating user memory |
| Long Text: | An illegal size or null pointer was specified for user memory. |
| Repair Text: | From Oracle doc: Specify a legal size and a valid pointer for user memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user already authenticated |
| Long Text: | A user has already been authenticated on this service handle. |
| Repair Text: | From Oracle doc: Terminate the service context before using it for another user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | service handle not initialized |
| Long Text: | The server context does not done exist. |
| Repair Text: | From Oracle doc: Establish the server context in the service context. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal attribute type |
| Long Text: | An illegal attribute type was specified for the handle. |
| Repair Text: | From Oracle doc: Consult the Oracle Call Interface Programmer's Guide. to specify an attribute valid for this handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal handle type |
| Long Text: | An illegal handle type was specified. |
| Repair Text: | From Oracle doc: Consult the Oracle Call Interface Programmer's Guide. to specify a valid handle type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | define handle used in a different position |
| Long Text: | A define was done with an existing handle on a different position. |
| Repair Text: | From Oracle doc: Specify the same position as before on a redefine. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | call not allowed for scalar data types |
| Long Text: | This call is valid only for object types. |
| Repair Text: | From Oracle doc: Verify that the data-type for this variable is an object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to allocate memory |
| Long Text: | Process was unable to allocate memory to store diagnostics. |
| Repair Text: | From Oracle doc: Terminate other processes in order to reclaim needed memory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24320 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to initialize a mutex |
| Long Text: | An attempt to initialize a MUTEX failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inconsistent parameters passed |
| Long Text: | One of the three memory function pointers is null or non-null. |
| Repair Text: | From Oracle doc: Verify that either all the memory functions are null or non-null. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to delete an initialized mutex |
| Long Text: | An attempt to delete an initialized MUTEX failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24323 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | value not allowed |
| Long Text: | A null or invalid value was passed in for a mandatory parameter. |
| Repair Text: | From Oracle doc: Verify that all mandatory parameters are properly initialized. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24324 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | service handle not initialized |
| Long Text: | An attempt was made to use an improper service context handle. |
| Repair Text: | From Oracle doc: Verify that the service context handle has all the parameters initialized prior to this call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24325 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this OCI operation is not currently allowed |
| Long Text: | An attempt was made to use a context handle outside its scope. |
| Repair Text: | From Oracle doc: Verify that the context handle is set to a service context handle that has been converted to a logon data area for other OCI calls. The logon data area must be converted back to a service context before it can be used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24326 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | handle passed in is already initialized |
| Long Text: | An attempt was made to pass an initialized handle. |
| Repair Text: | From Oracle doc: Verify that the parameter passed in to retrieve a handle does not already point to a handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24327 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | need explicit attach before authenticating a user |
| Long Text: | A server context must be initialized before creating a session. |
| Repair Text: | From Oracle doc: Create and initialize a server handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24328 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal attribute value |
| Long Text: | The attribute value passed in is illegal. |
| Repair Text: | From Oracle doc: Consult the Oracle Call Interface Programmer's Guide. and specify a legal attribute value for the handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24329 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid character set identifier |
| Long Text: | The character set identifier specified is invalid. |
| Repair Text: | From Oracle doc: Specify a valid character set identifier in the OCI call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24330 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal OCI error |
| Long Text: | An internal OCI error has occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24331 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user buffer too small |
| Long Text: | The user buffer to contain the output data is too small. |
| Repair Text: | From Oracle doc: Specify a bigger buffer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24332 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid object type |
| Long Text: | An invalid object type is requested for the describe call. |
| Repair Text: | From Oracle doc: Specify a valid object type to the describe call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24333 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | zero iteration count |
| Long Text: | An iteration count of zero was specified for the statement. |
| Repair Text: | From Oracle doc: Specify the number of times this statement must be executed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24334 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no descriptor for this position |
| Long Text: | The application is trying to get a descriptor from a handle for an illegal position. |
| Repair Text: | From Oracle doc: Check the position number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot support more than 1000 columns |
| Long Text: | The number of columns exceeds the maximum number supported. |
| Repair Text: | From Oracle doc: Specify a number of columns less than 1000. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24336 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid result set descriptor |
| Long Text: | The result set descriptor should have valid data fetched into it before it can be converted to a statement handle. |
| Repair Text: | From Oracle doc: Fetch valid data into the descriptor before attempting to convert it into a statement handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24337 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | statement handle not prepared |
| Long Text: | A statement cannot be executed before making preparing a request. |
| Repair Text: | From Oracle doc: Prepare a statement before attempting to execute it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24338 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | statement handle not executed |
| Long Text: | A fetch or describe was attempted before executing a statement handle. |
| Repair Text: | From Oracle doc: Execute a statement and then fetch or describe the data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24339 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot set server group name after connecting to server |
| Long Text: | An attempt was made to set the server group in a server handle after connecting to the server. However, once the connection is established to a server, the server group name cannot be set anymore. |
| Repair Text: | From Oracle doc: Attach to the server after setting the server group name in the server handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot support more than 255 columns |
| Long Text: | The number of columns exceeds maximum supported by the server. |
| Repair Text: | From Oracle doc: Limit your operation to 255 columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bad mode specified |
| Long Text: | OCI_ENV_NO_MUTEX mode was specified for a non-threaded client. |
| Repair Text: | From Oracle doc: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been specified at process initialization. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to destroy a mutex |
| Long Text: | An attempt to destroy a MUTEX failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24343 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user defined callback error |
| Long Text: | The only valid return value for a user defined callback function is OCI_CONTINUE. Any other value will cause this error. |
| Repair Text: | From Oracle doc: Make sure that OCI_CONTINUE is returned from the user-defined callback function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | success with compilation error |
| Long Text: | A SQL or PL/SQL compilation error occurred. |
| Repair Text: | From Oracle doc: Return OCI_SUCCESS_WITH_INFO along with the error code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | A Truncation or null fetch error occurred |
| Long Text: | A truncation or a null fetch error. |
| Repair Text: | From Oracle doc: Make sure that the buffer size is long enough to store the returned data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24346 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot execute without binding variables |
| Long Text: | None of the bind variables in the SQL statement are bound. |
| Repair Text: | From Oracle doc: Bind all the variables before the execute is done. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24347 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Warning of a NULL column in an aggregate function |
| Long Text: | A null column was processed by an aggregate function. |
| Repair Text: | From Oracle doc: An OCI_SUCCESS_WITH_INFO is returned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24348 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Update or Delete without Where |
| Long Text: | An UPDATE or DELETE was executed without a WHERE clause. |
| Repair Text: | From Oracle doc: An OCI_SUCCESS_WITH_INFO is returned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCI call not allowed |
| Long Text: | OCI used is not permitted from external procedures. |
| Repair Text: | From Oracle doc: Refer to the Oracle Call Interface Programmer's Guide. for usage restrictions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid date passed into OCI call |
| Long Text: | A bad date was passed into one of the OCI calls. |
| Repair Text: | From Oracle doc: Check your date bind values and correct them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid COBOL display type passed into OCI call |
| Long Text: | A bad COBOL display type was passed into one of the OCI calls. |
| Repair Text: | From Oracle doc: Check your COBOL display type bind values and correct them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user buffer too small to accommodate COBOL display type |
| Long Text: | User supplied buffer for a COBOL display type was too small to accommodate fetched number. |
| Repair Text: | From Oracle doc: Increase the allocation for COBOL display type buffer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number fetched too large to fit in COBOL display type buffer. |
| Long Text: | The number fetched was beyond the range that can be displayed. |
| Repair Text: | From Oracle doc: Check the number in the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24355 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to store a negative number in an Unsigned Display type. |
| Long Text: | An attempt was made to convert a negative number into an unsigned display type. |
| Repair Text: | From Oracle doc: Check the number in the database or change the defined datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24356 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error while converting from to COBOL display type. |
| Long Text: | An internal error was encountered during conversion to COBOL display type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24357 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error while converting from to OCIDate. |
| Long Text: | An internal error was encountered during conversion to OCIDate type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24358 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCIBindObject not invoked for a Object type or Reference |
| Long Text: | OCIBindObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference. |
| Repair Text: | From Oracle doc: Invoke the OCIBindObject call for all Object Types and References. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24359 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCIDefineObject not invoked for a Object type or Reference |
| Long Text: | OCIDefineObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference. |
| Repair Text: | From Oracle doc: Invoke the OCIDefineObject call for all Object Types and References. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Type Descriptor Object not specified for Object Bind/Define |
| Long Text: | Type Descriptor Object is a mandatory parameter for Object Types Binds and Defines. |
| Repair Text: | From Oracle doc: Invoke the OCIBindObject() or OCIDefineObject() call with a valid Type Descriptor Object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | basic bind call not invoked before invoking advanced bind call |
| Long Text: | One of the basic bind calls was not invoked on this bind handle before performing an advanced bind call. |
| Repair Text: | From Oracle doc: Invoke the advanced bind call on this bind handle only after performing a basic bind call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | improper use of the character count flag |
| Long Text: | When the character count flag is set, then the maximum size of the buffer in the server should be specified as a non-zero value. |
| Repair Text: | From Oracle doc: Use a non-zero value for the maximum size of the buffer in the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | measurements in characters illegal here |
| Long Text: | Measurements in characters instead of bytes are illegal if either the server's or client's character set is varying width. |
| Repair Text: | From Oracle doc: If either the client's or server's character set is varying width then do not use the OCI_ATTR_CHAR_COUNT attribute for the bind handle. Use OCI_ATTR_MAXDATA_SIZE instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24364 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error while padding blanks |
| Long Text: | An internal error has occurred while attempting to blank pad string data. This error should not occur normally. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24365 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in character conversion |
| Long Text: | This usually occurs during conversion of a multibyte character data when the source data is abnormally terminated in the middle of a multibyte character. |
| Repair Text: | From Oracle doc: Make sure that all multibyte character data is properly terminated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24366 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | migratable user handle is set in service handle |
| Long Text: | This occurs during user authentication, a migratable user handle has been set in the service handle. |
| Repair Text: | From Oracle doc: Service handle must not be set with migratable user handle when it is used to authenticate another user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24367 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user handle has not been set in service handle |
| Long Text: | This occurs during authentication of a migratable user. the service handle has not been set with non-migratable user handle. |
| Repair Text: | From Oracle doc: Service handle must be set with non-migratable user handle when it is used to authenticate a migratable user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24368 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCI mutex counter non-zero when freeing a handle |
| Long Text: | This is an internal OCI error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | required callbacks not registered for one or more bind handles |
| Long Text: | No callbacks have been registered for one or more of the bind handles which are part of the RETURNING clause. |
| Repair Text: | From Oracle doc: The bind handles which are to receive data in a DML statement with a RETURNING clause must have their mode set as DATA_AT_EXEC and callback functions must be registered for these bind handles using OCIBindDynamic. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24370 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal piecewise operation attempted |
| Long Text: | Data of a certain datatype that does not support piecewise operation is being sent or fetched in pieces. |
| Repair Text: | From Oracle doc: Always set the piece value to OCI_ONE_PIECE for datatypes that does not support piecewise operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24371 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data would not fit in current prefetch buffer |
| Long Text: | An internal OCI error has occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24372 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid object for describe |
| Long Text: | The object to be described is not valid. It either has compilation or authorization errors. |
| Repair Text: | From Oracle doc: The object to be described must be valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24373 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid length specified for statement |
| Long Text: | The length specified for the statement is either 0 or too large. |
| Repair Text: | From Oracle doc: Specify a valid length for the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24374 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | define not done before fetch or execute and fetch |
| Long Text: | The application did not define output variables for data being fetched before issuing a fetch call or invoking a fetch by specifying a non-zero row count in an execute call. |
| Repair Text: | From Oracle doc: Issue OCI define calls for the columns to be fetched. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24375 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot use V6 syntax when talking to a V8 server |
| Long Text: | V6 syntax is no longer supported in V8 server. |
| Repair Text: | From Oracle doc: Change syntax to V7 syntax or higher. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24376 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot register/get user callback for non-environment handle |
| Long Text: | A user callback registration or get was attempted on a handle which is not an environment handle. |
| Repair Text: | From Oracle doc: Pass the environment handle to register/get user callback. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24377 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid OCI function code |
| Long Text: | An invalid function code was used to register or get user callback. |
| Repair Text: | From Oracle doc: Use a valid OCI function code. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24378 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user callbacks not allowed for this call |
| Long Text: | An attempt was made to register a user callback for an OCI call for which it not allowed to register user callbacks. |
| Repair Text: | From Oracle doc: Do not register user callback for this OCI call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24379 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid user callback type |
| Long Text: | An invalid type of user callback was specified. |
| Repair Text: | From Oracle doc: Specify a valid user callback type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24380 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid mode specification |
| Long Text: | The mode parameter in an OCIU* call is invalid. |
| Repair Text: | From Oracle doc: Use only a valid mode parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24381 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error(s) in array DML |
| Long Text: | One or more rows failed in the DML. |
| Repair Text: | From Oracle doc: Refer to the error stack in the error handle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24382 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | statement handled already executed or described |
| Long Text: | The statement handle was executed or described successfully before. |
| Repair Text: | From Oracle doc: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24383 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Overflow segment of an IOT cannot be described |
| Long Text: | The name specified in the OCIDescribeAny call referred to an IOT overflow segment. |
| Repair Text: | From Oracle doc: Use OCIDescribeAny to describe only documented objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24750 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect size of attribute |
| Long Text: | Transaction ID attribute size is incorrect. |
| Repair Text: | From Oracle doc: Verify that the size parameter is correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24752 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCI_TRANS_NEW flag must be specified for local transactions |
| Long Text: | Application attempted to start a local transaction without using OCI_TRANS_NEW. |
| Repair Text: | From Oracle doc: Use OCI_TRANS_NEW when starting local transactions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24753 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | local transactions cannot be detached |
| Long Text: | An attempt to detach a local transaction was made. |
| Repair Text: | From Oracle doc: Local transactions may only be committed or rolled back. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24754 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start new transaction with an active transaction |
| Long Text: | An attempt to start a new transaction was made when there was an active transaction. |
| Repair Text: | From Oracle doc: Commit, rollback or detach the existing transaction before starting a new transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24755 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported |
| Long Text: | These flags are currently not supported. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24756 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction does not exist |
| Long Text: | An invalid transaction identifier or context was used or the transaction has completed. |
| Repair Text: | From Oracle doc: Supply a valid identifier if the transaction has not completed and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24757 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate transaction identifier |
| Long Text: | An attempt was made to start a new transaction with an identifier already in use by an existing transaction. |
| Repair Text: | From Oracle doc: Verify that the identifier is not in use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24758 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not attached to the requested transaction |
| Long Text: | An attempt was made to detach or complete a transaction that is not the current transaction. |
| Repair Text: | From Oracle doc: Verify that the transaction context refers to the current transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24759 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid transaction start flags |
| Long Text: | An invalid transaction start flag was passed. |
| Repair Text: | From Oracle doc: Verify that one of the values OCI_TRANS_NEW, OCI_TRANS_JOIN, or OCI_TRANS_RESUME was specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24760 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid isolation level flags |
| Long Text: | An invalid isolation level flag was passed. |
| Repair Text: | From Oracle doc: Verify that only one of following values - OCI_TRANS_READONLY, OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24761 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction rolled back |
| Long Text: | The application tried to commit a transaction and the server rolled it back. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24762 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | server failed due to unspecified error |
| Long Text: | An internal error has occurred in the server commit protocol. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24763 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction operation cannot be completed now |
| Long Text: | The commit or rollback cannot be performed now because the session cannot switch to the specified transaction. |
| Repair Text: | From Oracle doc: Retry the operation later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24764 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | transaction branch has been heuristically committed |
| Long Text: | This is an informational message. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24765 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | transaction branch has been heuristically rolled back |
| Long Text: | This is an informational message. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24766 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | transaction branch has been partly committed and aborted |
| Long Text: | This is an informational message. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24767 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | transaction was read-only and has been committed |
| Long Text: | This is an informational message. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24768 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | commit protocol error occured in the server |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24769 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot forget an active transaction |
| Long Text: | Transaction identifier refers to an active transaction. |
| Repair Text: | From Oracle doc: Verify that the identifier of an active transaction was not passed as an argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24770 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot forget a prepared transaction |
| Long Text: | Transaction identifier refers to a prepared transaction. |
| Repair Text: | From Oracle doc: Verify that the identifier of a prepared transaction was not passed as an argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24771 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot detach, prepare or forget a local transaction |
| Long Text: | Service handle contains a local transaction context. |
| Repair Text: | From Oracle doc: Verify that the transaction context does not refer to a local transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24772 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot mix tightly-coupled and loosely-coupled branches |
| Long Text: | Application attempted to start a transaction with a global transaction identifier and a wrong option. |
| Repair Text: | From Oracle doc: Verify that all branches of a global transaction are started with either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and uses distributed updates, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24773 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid transaction type flags |
| Long Text: | OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified. |
| Repair Text: | From Oracle doc: Verify that the right parameters are being used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24774 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot switch to specified transaction |
| Long Text: | The transaction specified in the call refers to a transaction created by a different user. |
| Repair Text: | From Oracle doc: Create transactions with the same authentication so that they can be switched. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24775 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot prepare or commit transaction with non-zero lock value |
| Long Text: | An attempt was made to detach the transaction with a non-zero lock value. |
| Repair Text: | From Oracle doc: Detach the transaction with lock value set to zero and then try to prepare or commit the transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24776 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot start a new transaction |
| Long Text: | An attempt was made to start a new transaction when session was already attached to an existing transaction. |
| Repair Text: | From Oracle doc: End the current transaction before creating a new transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24777 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | use of non-migratable database link not allowed |
| Long Text: | The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multithreaded server process. |
| Repair Text: | From Oracle doc: Perform the work in the local database or open a connection to the remote database from the client. If the multithreaded server option is installed, connect to the Oracle instance through the dispatcher. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24778 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot open connections |
| Long Text: | The migratable transaction tried to access a remote database when the session itself had opened connections to remote database(s). |
| Repair Text: | From Oracle doc: Close the connection(s) in the session and then try to access the remote database from the migratable transaction. If the error still occurs, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24779 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | detach not allowed with open remote cursor |
| Long Text: | The migratable transaction tried to detach from the current session while an open remote cursor exists. |
| Repair Text: | From Oracle doc: Close any open remote cursor prior to detach. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24780 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot recover a transaction while in an existing transaction |
| Long Text: | An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is idle too long). |
| Repair Text: | From Oracle doc: Detach from the current transaction and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24781 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | branches don't belong to the same global transaction |
| Long Text: | The list of xids passed into kpotxmp() do not have the same gtrid |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal parameter value in OCI lob function |
| Long Text: | One of the parameter values in the OCI LOB function is illegal. |
| Repair Text: | From Oracle doc: Check every parameter in the OCI Lob function call to make sure they are correct. Offsets should be greater than or equal to one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user defined lob read callback error |
| Long Text: | The only valid return value for a user defined LOB read callback function is OCI_CONTINUE. Any other value will cause this error. |
| Repair Text: | From Oracle doc: Verify that OCI_CONTINUE is returned from the user defined LOB read callback function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal parameter value in lob read function |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: This error should not normally occur. If it persists, contact your Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal parameter value in lob write function |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: This error should not normally occur. If it persists, contact your Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24805 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOB type mismatch |
| Long Text: | When copying or appending LOB locators, both source and destination LOB locators should be of the same type. |
| Repair Text: | From Oracle doc: Pass the same type of LOB locators for copying or appending. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24806 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOB form mismatch |
| Long Text: | When reading from or writing into LOBs, the character set form of the user buffer should be same as that of the LOB. |
| Repair Text: | From Oracle doc: Make sure that the buffer you are using to read or write has the same form as that of the LOB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24807 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOB form mismatch |
| Long Text: | When copying or appending LOBs, both source and destination LOB locators should have the same character set form. |
| Repair Text: | From Oracle doc: Pass locators of the same character set form for copying or appending LOBs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24808 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | streaming of lob data is not allowed when using lob buffering |
| Long Text: | An attempt was made to stream LOB data via the polling mode or a callback when LOB buffering was enabled for the input LOB locator. |
| Repair Text: | From Oracle doc: Lob buffering is useful when reading/writing small amounts of LOB data so streaming should not be necessary. Rewrite the OCILobRead/OCILobWrite call so that it does not use streaming. If streaming of data is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the OCILobRead/OCILobWrite call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24809 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | amount specified will not fit in the lob buffers |
| Long Text: | LOB buffering is enabled for the input LOB locator so buffering will be used. However, the amount of LOB data to read or write is larger than what the LOB buffers can hold. |
| Repair Text: | From Oracle doc: Either disable buffering on the input LOB locator and reissue the command or pass a smaller amount. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempting to write more data than indicated |
| Long Text: | While writing into a LOB, more data was supplied than indicated. |
| Repair Text: | From Oracle doc: If data is written in pieces, then make sure that you do not provide more data in the pieces (cumulatively), than you indicated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | less data provided for writing than indicated |
| Long Text: | While writing into a LOB, less data was provided than indicated. |
| Repair Text: | From Oracle doc: If writing data in single pieces, then make sure that the buffer length specified is big enough to accommodate the data being provided. If data is written in pieces, then make sure that all the data has been provided before specifying OCI_LAST_PIECE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | character set conversion to or from UCS2 failed |
| Long Text: | If the database character set is varying-width, the CLOB/NCLOB value is implicitly converted to or from UCS2. This implicit conversion failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot send or receive an unsupported LOB |
| Long Text: | An attempt was made to send a LOB across the network, but either the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and server are running different versions of Oracle. |
| Repair Text: | From Oracle doc: Use a version of the Oracle that supports the LOB on both the client and the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24850 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to startup shared subsystem |
| Long Text: | While attempting to initialize OCI in shared mode, a problem was encountered in starting the shared subsystem. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24851 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to connect to shared subsystem |
| Long Text: | While attempting to initialize OCI in shared mode, a problem was encountered in connecting the process to the shared subsystem. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24852 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | protocol error during statement execution |
| Long Text: | An internal protocol error occurred while receiving describe data from the server during execution of a statement. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24853 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to connect thread to shared subsystem |
| Long Text: | While attempting to initialize OCI in shared mode, a problem was encountered in connecting the thread to the shared subsystem. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24900 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or unsupported mode paramater passed in call |
| Long Text: | The mode parameter passed into the OCI Client Notification call is incorrect. |
| Repair Text: | From Oracle doc: Correct the mode parameter passed into OCI. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24901 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | handles belonging to different environments passed into an OCI call |
| Long Text: | All handles passed into an OCI call should belong to the same environment. In the call that returned this error, handles belonging to different environments were passed in. |
| Repair Text: | From Oracle doc: Make sure that the handle parameters in the call to come from the same OCI Environment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24902 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid subscription name or name-length in subscription handle |
| Long Text: | The subscription handle passed into the OCI call does not have a proper name or name-length attribute. |
| Repair Text: | From Oracle doc: Set the name and name-length attributes using the OCIAttrSet() call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24903 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid namespace attribute passed into OCI call |
| Long Text: | The subscription handle passed into the OCI call does not have a proper NAMESPACE attribute. |
| Repair Text: | From Oracle doc: Set the NAMESPACE attribute using the OCIAttrSet() call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-24904 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid callback attribute passed into OCI call |
| Long Text: | The subscription handle passed into the OCI call does not have a proper callback attribute. |
| Repair Text: | From Oracle doc: Set the callback attribute using the OCIAttrSet() call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid use of bind variable in trigger WHEN clause |
| Long Text: | A bind variable was used in the when clause of a trigger. |
| Repair Text: | From Oracle doc: Remove the bind variable. To access the table columns use (new/old).column_name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create this trigger type on views |
| Long Text: | Only INSTEAD OF triggers can be created on a view. |
| Repair Text: | From Oracle doc: Change the trigger type to INSTEAD OF. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create INSTEAD OF triggers on tables |
| Long Text: | Only BEFORE or AFTER triggers can be created on a table. |
| Repair Text: | From Oracle doc: Change the trigger type to BEFORE or AFTER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change NEW values for this column type in trigger |
| Long Text: | Attempt to change NEW trigger variables of datatype object, REF, nested table, VARRAY or LOB datatype which is not supported. |
| Repair Text: | From Oracle doc: Do not change the NEW trigger variables in the trigger body. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | WHEN clause is not allowed in INSTEAD OF triggers |
| Long Text: | WHEN clause is specified in an INSTEAD OF trigger. |
| Repair Text: | From Oracle doc: Remove the WHEN clause when creating an INSTEAD OF trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot CREATE INSTEAD OF trigger on a read-only view |
| Long Text: | Attempt to create an INSTEAD OF trigger on a view created with read-only option. The view cannot be updated using INSTEAD OF triggers. |
| Repair Text: | From Oracle doc: Do not create the trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify this column in UPDATE OF clause |
| Long Text: | Attempt to create a trigger on update of a column whose datatype is disallowed in the clause, such as LOB and nested table. |
| Repair Text: | From Oracle doc: Remove the UPDATE OF clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | functions or methods not allowed in WHEN clause |
| Long Text: | PL/SQL function call or method invocation is not allowed in the WHEN clause when creating a trigger. |
| Repair Text: | From Oracle doc: Remove the function call or method invocation from the WHEN clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no implicit conversion to LOB datatype in instead-of trigger |
| Long Text: | When inserting or updating a view using instead-of trigger, the new value for a LOB view column is of a different datatype. |
| Repair Text: | From Oracle doc: Specified a LOB value as the new value for the LOB view column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Nested table clause allowed only for INSTEAD OF triggers |
| Long Text: | Triggers on nested tables can only be created on view columns using INSTEAD OF triggers. |
| Repair Text: | From Oracle doc: Use view nested table columns for defining nested table triggers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid nested table column name in nested table clause |
| Long Text: | The column name specified in the nested table clause of an INSTEAD OF trigger does not correspond to a nested table column. |
| Repair Text: | From Oracle doc: Specify a nested table column on which the trigger is to be defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PARENT and NEW values cannot be identical |
| Long Text: | The referencing clause specifies identical values for PARENT and OLD. |
| Repair Text: | From Oracle doc: Respecify either the PARENT or NEW referencing value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OLD and PARENT values cannot be identical |
| Long Text: | The referencing clause specifies identical values for OLD and PARENT. |
| Repair Text: | From Oracle doc: Respecify either the OLD or PARENT referencing value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change the value of a PARENT reference variable |
| Long Text: | Parent values can only be read and not changed. |
| Repair Text: | From Oracle doc: Do not attempt to change a Parent variable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot perform DML on this nested table view column |
| Long Text: | DML cannot be performed on a nested table view column except through an INSTEAD OF trigger. |
| Repair Text: | From Oracle doc: Create an INSTEAD OF trigger over the nested table view column and then perform the DML. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify column list for insert into nested table view column |
| Long Text: | A column list cannot be specified for inserts into the nested table view column. |
| Repair Text: | From Oracle doc: Specify all the columns for insert into the nested table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot reference NEW ROWID for movable rows in before triggers |
| Long Text: | NEW ROWID was referenced in a before row trigger which is defined on an index-organized table, or a partitioned table with enabled movement of rows. The ROWID cannot be computed in a before row update trigger because it depends on the actual values of the row. |
| Repair Text: | From Oracle doc: Remove references to NEW ROWID from the trigger definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TABLESPACE option can only be used with ALTER INDEX REBUILD |
| Long Text: | The TABLESPACE option to ALTER INDEX was used without the REBUILD option. |
| Repair Text: | From Oracle doc: Use ALTER INDEX REBUILD TABLESPACE tablespace name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate REBUILD option specification |
| Long Text: | The REBUILD option to ALTER INDEX is specified more than once. |
| Repair Text: | From Oracle doc: Specify the option at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PARALLEL option can only be used with ALTER INDEX REBUILD |
| Long Text: | The PARALLEL option to ALTER INDEX was used without the REBUILD option. |
| Repair Text: | From Oracle doc: Use ALTER INDEX REBUILD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NOPARALLEL option can only be used with ALTER INDEX REBUILD |
| Long Text: | The NOPARALLEL option to ALTER INDEX was used without the REBUILD option. |
| Repair Text: | From Oracle doc: Use ALTER INDEX REBUILD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25104 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNRECOVERABLE option can only be used with ALTER INDEX REBUILD |
| Long Text: | The UNRECOVERABLE option to ALTER INDEX was used without the REBUILD option. |
| Repair Text: | From Oracle doc: Use ALTER INDEX REBUILD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RECOVERABLE option can only be used with ALTER INDEX REBUILD |
| Long Text: | The RECOVERABLE option to ALTER INDEX was used without the REBUILD option. |
| Repair Text: | From Oracle doc: Use ALTER INDEX REBUILD. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only one of PARALLEL or NOPARALLEL clause may be specified |
| Long Text: | PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in an ALTER INDEX REBUILD statement. |
| Repair Text: | From Oracle doc: Remove all but one of the PARALLEL or NOPARALLEL clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate TABLESPACE option specification |
| Long Text: | the TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement. |
| Repair Text: | From Oracle doc: Remove all but one of the TABLESPACE clauses. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby lock name space exceeds size limit of %s characters |
| Long Text: | The lock name space for the standby database exceeded the maximum string length. |
| Repair Text: | From Oracle doc: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a character string of less than the specified characters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | standby lock name space has illegal character '%s' |
| Long Text: | An invalid lock name space was specified for the standby database. The lock name space for the standby database can only contain A-Z, 0-9, '_', '#', '$', '.' and '@' characters. |
| Repair Text: | From Oracle doc: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a valid character string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NOSORT may not be used with a bitmap index |
| Long Text: | An attempt was made to create a bitmap index using the NOSORT option. |
| Repair Text: | From Oracle doc: Remove NOSORT from the CREATE BITMAP INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | creation of BITMAP cluster indices is not supported |
| Long Text: | An attempt was made to create a cluster index with the BITMAP attribute. |
| Repair Text: | From Oracle doc: Remove BITMAP from the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of BITMAP index columns is 30 |
| Long Text: | Too many columns were specified for the index. |
| Repair Text: | From Oracle doc: Create an index on fewer columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GLOBAL may not be used with a bitmap index |
| Long Text: | An attempt was made to create a bitmap index using the GLOBAL option. |
| Repair Text: | From Oracle doc: Remove GLOBAL from the CREATE BITMAP INDEX statement, and/or add a LOCAL partition descriptor if the table is partitioned. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid file number specified in the DUMP DATAFILE/TEMPFILE command |
| Long Text: | An invalid file number was used in dumping a datafile or temporary file. |
| Repair Text: | From Oracle doc: Specify a valid file number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate BLOCK option specification |
| Long Text: | BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command. |
| Repair Text: | From Oracle doc: Specify only one BLOCK option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid block number specified in the DUMP DATAFILE/TEMPFILE command |
| Long Text: | An invalid block number was used in dumping a datafile or temporary file. |
| Repair Text: | From Oracle doc: Specify a valid block number. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25117 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | MIN/MAX/Block Number expected |
| Long Text: | A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25118 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | invalid DUMP DATAFILE/TEMPFILE option |
| Long Text: | An invalid option was specified for the DUMP DATAFILE/TEMPFILE command. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25119 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LOGGING/NOLOGGING option already specified |
| Long Text: | In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once. |
| Repair Text: | From Oracle doc: Remove all but one of the logging specifications. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MINIMUM EXTENT option already specified |
| Long Text: | In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once. |
| Repair Text: | From Oracle doc: Remove all but one of the MINIMUM EXTENT specifications. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MINIMUM EXTENT value greater than maximum extent size |
| Long Text: | In CREATE/ALTER TABLESPACE, the value specified for the MINIMUM EXTENT option was greater than the maximum extent size. |
| Repair Text: | From Oracle doc: Choose a lower value for the MINIMUM EXTENT option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Only LOCAL bitmap indexes are permitted on partitioned tables |
| Long Text: | An attempt was made to create a global bitmap index on a partitioned table. |
| Repair Text: | From Oracle doc: Create a local bitmap index instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Too many components specified in the name. |
| Long Text: | More components per name than is allowed were specified. |
| Repair Text: | From Oracle doc: Check the name specified for the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Database link name not allowed. |
| Long Text: | A database link name was specified when it is not permitted. |
| Repair Text: | From Oracle doc: Check the name specified for the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | BUFFER_POOL storage option not allowed |
| Long Text: | An attempt was made to specify the BUFFER_POOL storage option. This option may only be specified during CREATE/ALTER TABLE/CLUSTER/INDEX. |
| Repair Text: | From Oracle doc: Remove this option and retry the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid name specified for BUFFER_POOL |
| Long Text: | The name of the buffer pool specified by the user is invalid. The only valid names are KEEP, RECYCLE and DEFAULT. |
| Repair Text: | From Oracle doc: Use a valid name or remove the BUFFER_POOL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RELY not allowed in NOT NULL constraint |
| Long Text: | An attempt was made to set RELY on for NOT NULL constraint. |
| Repair Text: | From Oracle doc: Only NORELY may be specified for a NOT NULL constraint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | No insert/update/delete on table with constraint (%s.%s) disabled and validated |
| Long Text: | An attempt was made to insert/update/delete on table with DISABLE VALIDATE constraint. |
| Repair Text: | From Oracle doc: Change the constraint's states. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25129 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify constraint (%s) - no such constraint |
| Long Text: | The named constraint does not exist for this table. |
| Repair Text: | From Oracle doc: Try again with a constraint that does exist for this table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25130 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot modify primary key - primary key not defined for table |
| Long Text: | An attempt was made to modify a primary key that is not defined for the table. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25131 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot modify unique(%s) - unique key not defined for table |
| Long Text: | An attempt was made to modify a unique key that is not defined for the table. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25132 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNIQUE constraint (%s.%s) disabled and validated in ALTER TABLE EXCHANGE PARTITION |
| Long Text: | Cannot ALTER TABLE EXCHANGE PARTITION when the partition and the table have a disabled and validated unique constraints AND the unique keys in the partition is not mutually exclusive from the rest of the table. |
| Repair Text: | From Oracle doc: Change the constraint's status. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25133 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate SINGLE TABLE option specified |
| Long Text: | The SINGLE TABLE option was specified more than once. |
| Repair Text: | From Oracle doc: Specify the SINGLE TABLE option only once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25134 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword TABLE expected |
| Long Text: | The keyword TABLE is missing from the SINGLE TABLE option. |
| Repair Text: | From Oracle doc: Place the keyword TABLE after the keyword SINGLE in the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25135 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use the SINGLE TABLE option |
| Long Text: | The SINGLE TABLE option is only valid for hash clusters. |
| Repair Text: | From Oracle doc: Do not specify the SINGLE TABLE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25136 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this cluster can contain only one table |
| Long Text: | An attempt was made to store more than one table in a cluster that was created with the SINGLE TABLE option. |
| Repair Text: | From Oracle doc: Do not attempt to store more than one table in the cluster. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25137 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Data value out of range |
| Long Text: | Value from cast operand is larger than cast target size. |
| Repair Text: | From Oracle doc: Increase size of cast target. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25138 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s initialization parameter has been made obsolete |
| Long Text: | An obsolete initialization parameter has been specified. |
| Repair Text: | From Oracle doc: The system will come up, but parameters must be examined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25139 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for CREATE TEMPORARY TABLESPACE |
| Long Text: | An invalid option appears. |
| Repair Text: | From Oracle doc: Specify one of the valid options: TEMPFILE, EXTENT MANAGEMENT LOCAL, UNIFORM. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25140 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s space policy cannot be specified for the %s extent management |
| Long Text: | An invalid option appears. |
| Repair Text: | From Oracle doc: Make sure that for LOCAL extent management UNIFORM or AUTOALLOCATE is specified, and for DICTIONARY extent management UNIFORM or AUTOALLOCATE are not specified |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25141 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid EXTENT MANAGEMENT clause |
| Long Text: | An invalid option appears for EXTENT MANAGEMENT clause. |
| Repair Text: | From Oracle doc: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25142 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | default storage clause specified twice |
| Long Text: | Default storage clause was specified twice for create tablespace. |
| Repair Text: | From Oracle doc: Specify it once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25143 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | default storage clause is not compatible with allocation policy |
| Long Text: | Default storage clause was specified for a tablespace with AUTOALLOCATE or UNIFORM policy. |
| Repair Text: | From Oracle doc: Omit the storage clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25144 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for CREATE TABLESPACE with TEMPORARY contents |
| Long Text: | An invalid option appears. |
| Repair Text: | From Oracle doc: Specify one of the valid options: EXTENT MANAGEMENT DICTIONARY, USER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25145 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | allocation policy already specified |
| Long Text: | In CREATE TABLESPACE, the allocation policy was specified more than once, for example, AUTOALLOCATE and UNIFORM. |
| Repair Text: | From Oracle doc: Remove all but one of the allocation policy specifications. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25146 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | EXTENT MANAGEMENT option already specified |
| Long Text: | In CREATE TABLESPACE, the EXTENT MANAGEMENT option was specified more than once. |
| Repair Text: | From Oracle doc: Remove all but one of the EXTENT MANAGEMENT specifications. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25147 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNIFORM SIZE value greater than maximum extent size |
| Long Text: | In CREATE/ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size. |
| Repair Text: | From Oracle doc: Choose a lower value for the UNIFORM SIZE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25148 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ONLINE option not permitted |
| Long Text: | An attempt was made to specify ONLINE for ALTER TABLE MOVE on a table that is not index-organized. The ONLINE option is currently supported only for index-organized tables. |
| Repair Text: | From Oracle doc: Remove the ONLINE option from the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25149 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Columns of UROWID type may not be indexed |
| Long Text: | An attempt was made to create an index on a column of UROWID type. |
| Repair Text: | From Oracle doc: Remove the column from the list of indexed columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ALTERING of extent parameters not permitted |
| Long Text: | An attempt was made to alter the extent parameters for a segment in a tablespace with autoallocate or uniform extent allocation policy. |
| Repair Text: | From Oracle doc: Remove the appropriate extent parameters from the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Rollback Segment cannot be created in this tablespace |
| Long Text: | An attempt was made to create a rollback segment in a tablespace with autoallocate extent allocation policy. |
| Repair Text: | From Oracle doc: Specify a different tablespace for the rollback segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TEMPFILE cannot be dropped at this time |
| Long Text: | An attempt was made to drop a TEMPFILE being used by online users. |
| Repair Text: | From Oracle doc: The TEMPFILE has been taken offline. Try again later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Temporary Tablespace is Empty |
| Long Text: | An attempt was made to use space in a temporary tablespace with no files. |
| Repair Text: | From Oracle doc: Add files to the tablespace using ADD TEMPFILE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25175 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no PRIMARY KEY constraint found |
| Long Text: | A PRIMARY KEY constraint must be defined for a table with this organization. |
| Repair Text: | From Oracle doc: Define a PRIMARY KEY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25176 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | storage specification not permitted for primary key |
| Long Text: | Storage parameters cannot be defined for a PRIMARY KEY constraint for a table with this organization. |
| Repair Text: | From Oracle doc: Remove storage specification for primary key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25177 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | UNRECOVERABLE option not permitted |
| Long Text: | The UNRECOVERABLE option may not be specified for a primary key for a table with this organization. |
| Repair Text: | From Oracle doc: Remove UNRECOVERABLE option for primary key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25178 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate PCTTHRESHOLD storage option specification |
| Long Text: | The storage option PCTTHRESHOLD is specified more than once. |
| Repair Text: | From Oracle doc: Specify storage options at most once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25179 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid PCTTHRESHOLD storage option value |
| Long Text: | The specified value must be a positive integer. |
| Repair Text: | From Oracle doc: Specify an appropriate value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25180 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PCTTHRESHOLD only valid for certain table organizations |
| Long Text: | PCTTHRESHOLD can only be specified for tables with certain organizations. |
| Repair Text: | From Oracle doc: Remove the PCTTHRESHOLD option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25181 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing ON keyword for NESTED INDEX |
| Long Text: | The ON keyword is required to specify nested index column nest. |
| Repair Text: | From Oracle doc: Add ON keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25182 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | feature not currently available for index-organized tables |
| Long Text: | An attempt was made to use one or more of the following feature(s) not currently supported for index-organized tables: CREATE TABLE with LOB/BFILE/VARRAY columns partitioning/PARALLEL/CREATE TABLE AS SELECT options ALTER TABLE with ADD/MODIFY column options CREATE INDEX |
| Repair Text: | From Oracle doc: Do not use the disallowed feature(s) in this release. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25183 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index-organized table top index segment is in a different tablespace |
| Long Text: | An attempt was made to drop a tablespace which contains an index only table's overflow segment but not the top index segment. |
| Repair Text: | From Oracle doc: Find index-organized tables which span the tablespace being dropped and some other tablespace(s). Drop these tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25184 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column name expected |
| Long Text: | A column name is not present where required by the CREATE TABLE for specifying last column to be included in the index segment of the index-organized table. |
| Repair Text: | From Oracle doc: Specify a column name where required by the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25185 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index column other than last can not be specified for INCLUDE clause |
| Long Text: | An index column name other than the last was specified as including column. |
| Repair Text: | From Oracle doc: Specify either a column name which is not part of index-organized table primary key index, or the last key column of the primary key for the INCLUDING clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25186 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | INCLUDING clause specified for index-organized table without OVERFLOW |
| Long Text: | INCLUDING clause of a CREATE TABLE is an valid option only for index-organized tables with OVERFLOW clause (at creation time) or if an OVERFLOW segment already exists (at ALTER time). |
| Repair Text: | From Oracle doc: Specify OVERFLOW clause for the index-organized table: For ALTER, perform ADD OVERFLOW first. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25187 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified exceptions table form incorrect |
| Long Text: | The specified table does not have the proper field definitions. |
| Repair Text: | From Oracle doc: Specify the correct table to use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25188 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop/disable/defer the primary key constraint for index-organized tables |
| Long Text: | An attempt was made to DROP, DISABLE, or DEFER the primary key constraint for an index-only table. This is not allowed. |
| Repair Text: | From Oracle doc: Do not DROP, DISABLE, or DEFER the primary key constraint for an index-only table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25189 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal ALTER TABLE option for an index-organized table |
| Long Text: | During ALTER of a index-organized table, the user attempted to enter one or more of the following options: TABLESPACE, ALLOCATE/DEALLOCATE EXTENT, PCTFREE/PCTUSED for IOT top index segment |
| Repair Text: | From Oracle doc: Remove the illegal option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25190 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | an index-organized table maintenance operation may not be combined with other operations |
| Long Text: | ALTER TABLE statement attempted to combine an index-organized table maintenance operation (for example, changing physical attributes) with some other operation (for example, ADD constraint) which is illegal |
| Repair Text: | From Oracle doc: Ensure that a index-organized table maintenance operation is the sole operation specified in ALTER TABLE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25191 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot reference overflow table of an index-organized table |
| Long Text: | An attempt was made to directly access the overflow table of an index-organized table. |
| Repair Text: | From Oracle doc: Issue the statement against the parent index-organized table containing the specified overflow table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25192 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for an index-organized table |
| Long Text: | An attempt was made to specify one or more of the following options for an index-organized table: [NO]CACHE, NO LOGGING, CLUSTER. |
| Repair Text: | From Oracle doc: Remove the illegal option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25193 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot use COMPRESS option for a single column key |
| Long Text: | An attempt was made to use COMPRESS option on single column key. |
| Repair Text: | From Oracle doc: Remove the COMPRESS option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25194 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid COMPRESS prefix length value |
| Long Text: | The specified value must be a positive integer less than the number of key columns. |
| Repair Text: | From Oracle doc: Specify an appropriate value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25195 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for index on an index-organized table |
| Long Text: | An attempt was made to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED. |
| Repair Text: | From Oracle doc: Specify an appropriate option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25196 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword MOVE in ALTER TABLE MOVE must immediately follow table_name |
| Long Text: | MOVE specified after one/more other ALTER options. |
| Repair Text: | From Oracle doc: Change order of options, MOVE should be first or remove the illegal option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25197 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | an overflow segment already exists for the indexed-organized table |
| Long Text: | An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25198 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only range partitioning is supported for index-organized table |
| Long Text: | Hash, system, or composite partitioning schemes are not supported. |
| Repair Text: | From Oracle doc: Select a different partitioning scheme. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25199 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partitioning key of a index-organized table must be a subset of the primary key |
| Long Text: | An attempt was made to specify a partitioning key which is not a prefix of the primary key of the index-organized table. |
| Repair Text: | From Oracle doc: Select a different partitioning key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, QUEUE_NAME should be [SCHEMA.]NAME |
| Long Text: | A NULL parameter was specified for QUEUE_NAME. |
| Repair Text: | From Oracle doc: Specify a non-NULL queue name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE |
| Long Text: | An invalid value specified for parameter VISIBILITY. |
| Repair Text: | From Oracle doc: Specify either ON_COMMIT or IMMEDIATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value NULL, %s should be non-NULL |
| Long Text: | A NULL value was specified for the parameter. |
| Repair Text: | From Oracle doc: Specify a non-NULL value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, DELAY should be non-negative |
| Long Text: | A negative value or NULL was specified for DELAY. |
| Repair Text: | From Oracle doc: Specify a non-negative integer for DELAY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP |
| Long Text: | An invalid SEQUENCE_DEVIATION was specified. |
| Repair Text: | From Oracle doc: Specify either the option 'BEFORE' or 'TOP'. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the QUEUE %s.%s does not exist |
| Long Text: | The specified queue does not exist. |
| Repair Text: | From Oracle doc: Create the queue first before specifying it for enqueue or dequeue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enqueue failed, enqueue to exception queue %s.%s not permitted |
| Long Text: | An attempt was made to enqueue to an exception queue. |
| Repair Text: | From Oracle doc: Try enqueueing to another queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enqueue failed, queue %s.%s is disabled from enqueueing |
| Long Text: | The queue has been stopped to prevent any further enqueueing. |
| Repair Text: | From Oracle doc: Enable the queue first by using an administrative operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE |
| Long Text: | A relative message identifier should be specified if sequence deviation is specified as BEFORE. |
| Repair Text: | From Oracle doc: Either specify an existing relative message identifier or do not specify sequence deviation as BEFORE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, EXPIRATION should be non-negative or NEVER |
| Long Text: | The expiration is less than zero or NULL. |
| Repair Text: | From Oracle doc: Specify a valid value for EXPIRE_AFTER which should be greater than or equal to zero or NEVER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value for RELATIVE_MSGID, no message in queue with that msgid |
| Long Text: | No message in the queue with the MSGID equal to the specified RELATIVE_MSGID. |
| Repair Text: | From Oracle doc: Try again with a valid RELATIVE_MSGID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25211 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid DELAY specified when using sequence deviation |
| Long Text: | The DELAY specified in the enqueue is greater than the delay of the message with the given relative message ID. |
| Repair Text: | From Oracle doc: Set the DELAY to be less than or equal to the delay of the message with the given relative message ID. If the TOP option is used the delay must be less than or equal to the delay of all the messages in the queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25212 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid PRIORITY specified when using sequence deviation |
| Long Text: | The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message ID. |
| Repair Text: | From Oracle doc: Set the PRIORITY to be less than the delay of the message with the given relative message ID. If the TOP option is used the priority must be greater than or equal to the priority of all the messages in the queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25213 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | message with specified RELATIVE_MSGID has been dequeued |
| Long Text: | The message specified by the RELATIVE_MSGID field in the sequence deviation BEFORE option has been dequeued. |
| Repair Text: | From Oracle doc: No action required. This is an informational message only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25215 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user_data type and queue type do not match |
| Long Text: | A user tries to enqueue an object to a queue that was created for objects of different type. |
| Repair Text: | From Oracle doc: Try enqueue again with an object of the right type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25216 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid recipient, either NAME or ADDRESS must be specified |
| Long Text: | Both attributes, NAME and ADDRESS, were specified null for one of the recipients in the recipient list. |
| Repair Text: | From Oracle doc: Specify a non-null NAME or ADDRESS for the recipient. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25217 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enqueue failed, visibility must be IMMEDIATE for queue %s.%s |
| Long Text: | An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE. |
| Repair Text: | From Oracle doc: Set visibility to IMMEDIATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25218 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enqueue failed, delay must be zero for queue %s.%s |
| Long Text: | An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds. |
| Repair Text: | From Oracle doc: Set delay to zero. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25219 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | enqueue failed, sequence deviation not allowed for queue %s.%s |
| Long Text: | An attempt was made to enqueue to a non-persistent queue with sequence deviation specified. |
| Repair Text: | From Oracle doc: Do not specify sequence deviation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25225 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED |
| Long Text: | An invalid parameter has been specified for DEQUEUE_MODE. |
| Repair Text: | From Oracle doc: Specify either REMOVE, BROWSE or LOCKED. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25226 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dequeue failed, queue %s.%s is not enabled for dequeue |
| Long Text: | The queue has not been enabled for dequeue. |
| Repair Text: | From Oracle doc: Enable the queue using START_QUEUE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25228 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | timeout or end-of-fetch during message dequeue from %s.%s |
| Long Text: | User-specified dequeue wait time has passed or the end of the queue has been reached but no message has been retrieved. |
| Repair Text: | From Oracle doc: Try dequeue again with the appropriate WAIT_TIME or the FIRST_MESSAGE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25230 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s, WAIT should be non-negative |
| Long Text: | A negative value has been specified for WAIT. |
| Repair Text: | From Oracle doc: Specify a non-negative value or FOREVER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot dequeue because CONSUMER_NAME not specified |
| Long Text: | A user tried to dequeue from a queue that has been created for multiple consumers but a CONSUMER_NAME was not been specified in the dequeue options. |
| Repair Text: | From Oracle doc: Specify the CONSUMER_NAME in the dequeue options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate recipients specified for message |
| Long Text: | An enqueue was performed with duplicate queue agents in the recipients parameter. |
| Repair Text: | From Oracle doc: Remove the duplicate queue agent and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25233 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid parameter specified for NAVIGATION |
| Long Text: | An invalid parameter has been specified for NAVIGATION. |
| Repair Text: | From Oracle doc: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing the first message that satisfies the criterion, NEXT_MESSAGE for dequeuing the next message that satisfies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25234 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NEXT_TRANSACTION navigation option invalid for queue table %s.%s |
| Long Text: | The NEXT_TRANSACTION navigation option was used in a dequeue from a queue in a queue table that was not created for transactional grouping. |
| Repair Text: | From Oracle doc: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional grouping create the queue in a queue table that has transactional grouping enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25235 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fetched all messages in current transaction |
| Long Text: | The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction. |
| Repair Text: | From Oracle doc: Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25236 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buffer too small for user data |
| Long Text: | The variable or buffer used for the out parameter payload is too small for the user data dequeued. |
| Repair Text: | From Oracle doc: Increase the size of the buffer or the size of the variable. Maximum size allowed is 32K. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25237 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | navigation option used out of sequence |
| Long Text: | The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages. |
| Repair Text: | From Oracle doc: Reset the dequeuing position using the FIRST_MESSAGE navigation option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25238 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many recipients specified for message destination %s |
| Long Text: | An ENQUEUE was performed with more than 32 recipients for the given destination (address). |
| Repair Text: | From Oracle doc: Reduce the number of recipients to 32 or less, and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25239 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | message ID not supplied when dequeuing from exception queue %s.%s |
| Long Text: | An attempt was made to dequeue from a release 8.0-compatible exception queue without including a message ID in the dequeue options. |
| Repair Text: | From Oracle doc: Check the application to ensure that the queue name has been specified correctly. If the queue name is correct supply a message ID when dequeuing from a release 8.0-compatible exception queue. Otherwise, upgrade the QUEUE_TABLE containing the queue to release 8.1-compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25240 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | message ID and correlation ID specified in dequeue options |
| Long Text: | An attempt was made to dequeue by including both a message ID and a correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either one of message ID or correlation ID, or neither ID. |
| Repair Text: | From Oracle doc: To dequeue a message, specify a message ID or a correlation ID in the dequeue options, but do not specify both. If you want to dequeue in the queue's sort order, then do not specify either the message ID or correlation ID in the dequeue options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25241 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change correlation ID from %s to %s without FIRST_MESSAGE option |
| Long Text: | An attempt was made to change the correlation ID while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing. |
| Repair Text: | From Oracle doc: To use a correlation ID that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25242 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot change subscriber name from %s to %s without FIRST_MESSAGE option |
| Long Text: | An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing. |
| Repair Text: | From Oracle doc: To use a subscriber name that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25243 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CONSUMER_NAME cannot be specified when dequeuing from exception queue %s.%s |
| Long Text: | An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers. |
| Repair Text: | From Oracle doc: Specify only the message ID in the dequeue options to dequeue a message from an exception queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25244 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dequeue index key not found, QUEUE %s, rowid %s |
| Long Text: | An internal error was encountered. There may be an inconsistency in the queue table index. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. You may need to provide the trace file and information about reproducing the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25245 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | agent name cannot be specified if address is a single-consumer queue or an exception queue |
| Long Text: | The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue. |
| Repair Text: | From Oracle doc: Do not specify the agent name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25246 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | listen failed, the address %s is an 8.0 style exception queue |
| Long Text: | An 8.0 style exception queue was specified in the agent-list for the LISTEN call. |
| Repair Text: | From Oracle doc: Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25247 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s is not a recipient of specified message |
| Long Text: | The consumer name specified in the dequeue options is not a recipient of the message specified by the message ID. |
| Repair Text: | From Oracle doc: Ensure that the agent specified by the consumer name is a recipient of the message specified by the message ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25248 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate agent specified in the agent list |
| Long Text: | An agent was specified more than once in the agent list of the LISTEN call. |
| Repair Text: | From Oracle doc: Remove the duplicate agent specification(s), and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25249 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dequeue failed, dequeue not allowed for queue %s.%s |
| Long Text: | An attempt was made to dequeue from a non-persistent queue. |
| Repair Text: | From Oracle doc: Dequeue from a different queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot specify a remote recipient for the message |
| Long Text: | A recipient for the message enqueued to a non-persistent queue had a non-local address. |
| Repair Text: | From Oracle doc: Do not specify the address field or specify the queue which is the target of the enqueue |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded maximum number of recipients for message |
| Long Text: | An attempt was made to issue an ENQUEUE call that exceeded the maximum number (1024) of recipients per message. |
| Repair Text: | From Oracle doc: Reduce the number of recipients to 1024 or less, and retry the call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25252 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | listen failed, the address %s is a non-persistent queue |
| Long Text: | A non-persistent queue was specified as an address for an agent in the LISTEN call. |
| Repair Text: | From Oracle doc: Specify a normal queue as address for the agent, and retry the LISTEN call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25253 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | listen failed, queue %s.%s is not enabled for dequeue |
| Long Text: | An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call. |
| Repair Text: | From Oracle doc: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25254 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | time-out in LISTEN while waiting for a message |
| Long Text: | The specified wait time has elapsed and there were no messages for any of the agents in the agent-list. |
| Repair Text: | From Oracle doc: Try the LISTEN call with an appropriate time-out. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25255 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect subscription %s %s |
| Long Text: | An incorrect subscription string was specified with OCIRegister. |
| Repair Text: | From Oracle doc: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE form. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25256 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | consumer cannot be specified with a single-consumer queue or an exception queue |
| Long Text: | An attempt was made to specify a consumer in the subscription string when registering for notification on a single-consumer queue or an exception queue. |
| Repair Text: | From Oracle doc: Do not specify the consumer in the subscription string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25257 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | consumer must be specified with a multi-consumer queue |
| Long Text: | An attempt was made to register on a multi-consumer queue without specifying a consumer in the subscription string. |
| Repair Text: | From Oracle doc: Specify a consumer in the subscription string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25258 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot register for notifications on an 8.0 style exception queue |
| Long Text: | An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister. |
| Repair Text: | From Oracle doc: Specify a normal queue or a non-persistent queue. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25259 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify protocol for agent |
| Long Text: | The user specified the protocol attribute for an agent in the agent list. |
| Repair Text: | From Oracle doc: Do not specify the protocol attribute of the agent object type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25261 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation |
| Long Text: | AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation. |
| Repair Text: | From Oracle doc: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | agent name cannot be NULL if address is a multi-consumer queue |
| Long Text: | The name for the agent in the LISTEN call was not specified when the agent address was a multi-consumer queue. |
| Repair Text: | From Oracle doc: Specify a non-NULL name for the agent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25263 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no message in queue %s.%s with message ID %s |
| Long Text: | An attempt was made to dequeue a message with a specific message ID, but no such message exists in the queue. |
| Repair Text: | From Oracle doc: Try dequeue again with a valid message ID. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25276 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table specified is not a queue table |
| Long Text: | An invalid queue table name is specified. |
| Repair Text: | From Oracle doc: Check the dictionary views to see if the table is a queue table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25277 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot grant or revoke object privilege on release 8.0 compatible queues |
| Long Text: | An attempt was made to grant or revoke object privilege on release 8.0 style queues. |
| Repair Text: | From Oracle doc: Convert the release 8.0 compatible queue table to release 8.1 compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object privilege. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25278 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | grantee name cannot be NULL |
| Long Text: | An attempt was made to specify NULL for the grantee parameter. |
| Repair Text: | From Oracle doc: Specify a valid grantee parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of concurrent transaction branches exceeded |
| Long Text: | The limit on the number of concurrent transaction branches has been reached. |
| Repair Text: | From Oracle doc: Increase the initialization parameter TRANSACTIONS and restart the system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction is currently in use |
| Long Text: | The transaction is currently used by a different session. |
| Repair Text: | From Oracle doc: Do not switch to a transaction attached to some other session. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no current transaction |
| Long Text: | The user session is not attached to any transaction. |
| Repair Text: | From Oracle doc: Do not attempt to detach when there is no current transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | branch marked for deletion |
| Long Text: | The branch specified cannot be killed immediately because another session is using the branch, but it has been marked for kill. This means it will be deleted as soon as possible after the current uninterruptable operation is completed. |
| Repair Text: | From Oracle doc: No action is required for the branch to be deleted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must replay fetch |
| Long Text: | A failure occurred since the last fetch on this statement. Failover was able to bring the statement to its original state to allow continued fetches. |
| Repair Text: | From Oracle doc: This is an internally used error message and should not be seen by the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25401 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not continue fetches |
| Long Text: | A failure occurred since the last fetch on this statement. Failover was unable to bring the statement to its original state to allow continued fetches. |
| Repair Text: | From Oracle doc: Re-execute the statement and start fetching from the beginning. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25402 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction must roll back |
| Long Text: | A failure occurred while a transaction was active on this connection. |
| Repair Text: | From Oracle doc: The client must roll back. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25403 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not reconnect |
| Long Text: | The connection to the database has been lost, and attempts to reconnect have failed. |
| Repair Text: | From Oracle doc: Manually reconnect. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25404 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | lost instance |
| Long Text: | The primary instance has died. |
| Repair Text: | From Oracle doc: This is an internally used error message and should not be seen by the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25405 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transaction status unknown |
| Long Text: | A failure occurred while a transaction was attempting to commit. Failover could not automatically determine instance status. |
| Repair Text: | From Oracle doc: The user must determine the transaction's status manually. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25406 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not generate a connect address |
| Long Text: | Failover was unable to generate an address for a backup instance. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25407 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection terminated |
| Long Text: | The connection was lost while doing a fetch. |
| Repair Text: | From Oracle doc: This is an internally used error message and should not be seen by the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25408 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not safely replay call |
| Long Text: | The connection was lost while doing this call. It may not be safe to replay it after failover. |
| Repair Text: | From Oracle doc: Check to see if the results of the call have taken place, and then replay it if desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25425 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection lost during rollback |
| Long Text: | The connection was lost while issuing a rollback. |
| Repair Text: | From Oracle doc: If the transaction is not externally coordinated, then Oracle implicitly rolled back, so no action is required. Otherwise examine PENDING_TRANS$ to determine if ROLLBACK FORCE is required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25426 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote instance does not support shared dblinks |
| Long Text: | A shared database link is being used to connect to a remote instance that does not support this feature because it is an older version. |
| Repair Text: | From Oracle doc: Use a normal database link if you need to connect to this instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ruleset specified does not exist |
| Long Text: | An attempt to access a ruleset was made, but the ruleset referenced does not exist. |
| Repair Text: | From Oracle doc: Look up the correct name of the ruleset in USER_RULESETS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rule %s does not exist |
| Long Text: | An attempt to access a rule was made, which failed because the rule does not exist. |
| Repair Text: | From Oracle doc: Look up the rule in the rules storage table, which can be found from USER_RULESETS. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table specified does not exist |
| Long Text: | An attempt to define a ruleset on a table was made, which failed because the rule does not exist. |
| Repair Text: | From Oracle doc: Define rulesets only on existing tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25440 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate ruleset |
| Long Text: | An attempt to define a ruleset was made, which failed because a ruleset with the same name exists in the same schema. |
| Repair Text: | From Oracle doc: Define a ruleset with a different name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-25441 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate rule %s |
| Long Text: | An attempt to define a rule was made, which failed because a rule with the same name already exists in the same ruleset. |
| Repair Text: | From Oracle doc: Define a rule with a different name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition load specified but table %s is not partitioned |
| Long Text: | The Loader control file contains a PARTITION clause but the table being loaded is not partitioned. |
| Repair Text: | From Oracle doc: Remove the partition specification from the SQL*Loader control file and retry the load. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Index %s specified in SORTED INDEXES does not exist on table %s |
| Long Text: | A non-existent index was specified in the SORTED INDEXES clause. |
| Repair Text: | From Oracle doc: Do not specify as a SORTED INDEX. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Table %s has index defined upon it. |
| Long Text: | Parallel load was specified into a table which has index defined upon it. |
| Repair Text: | From Oracle doc: Drop index(es) defined upon table, or do not use parallel load, or use SKIP_INDEX_MAINTENANCE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parallel load not supported for index-organized table %s |
| Long Text: | Parallel load is not supported for index-organized tables. |
| Repair Text: | From Oracle doc: Load the index-organized table without the PARALLEL option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tables loaded through the direct path may not be clustered |
| Long Text: | An attempt was made to load a clustered table via the direct path. |
| Repair Text: | From Oracle doc: Use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | For INSERT option, table must be empty. Error on table %s |
| Long Text: | The user tried to use the INSERT option on a non-empty table. |
| Repair Text: | From Oracle doc: Empty the table from SQL*Plus, or use the REPLACE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NOT NULL column %s has a nullif clause |
| Long Text: | A column which is NOT NULL in the database has a SQL*Loader NULLIF clause on it. |
| Repair Text: | From Oracle doc: Remove the NULLIF clause in the SQL*Loader control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NOT NULL column %s has a defaultif clause which may evaluate to null |
| Long Text: | A column which is NOT NULL in the database has a SQL*Loader DEFAULTIF clause which may evaluate to null. |
| Repair Text: | From Oracle doc: Remove the DEFAULTIF clause in the SQL*Loader control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Column %s in table %s is NOT NULL and is not being loaded |
| Long Text: | A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected. |
| Repair Text: | From Oracle doc: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tables loaded through the direct path may not be object tables |
| Long Text: | An attempt was made to load an object table via the direct path. |
| Repair Text: | From Oracle doc: Use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tables loaded through the direct path may not have object columns |
| Long Text: | An attempt was made to load a table with an object column via the direct path. |
| Repair Text: | From Oracle doc: Use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tables loaded through the direct path may not be nested |
| Long Text: | An attempt was made to load a nested table via the direct path. |
| Repair Text: | From Oracle doc: Use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tables loaded through the direct path may not have REF columns |
| Long Text: | An attempt was made to load a table with a REF column via the direct path. |
| Repair Text: | From Oracle doc: Use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tables loaded through the direct path may not have array columns |
| Long Text: | An attempt was made to load a table with an array column via the direct path. |
| Repair Text: | From Oracle doc: Use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Record %s: Rejected - Error on table %s, partition %s |
| Long Text: | The record indicated caused an Oracle error on insert. |
| Repair Text: | From Oracle doc: Determine the Oracle error and correct the record. The offending column(s) are not known. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Global indexes not allowed on direct path partition load, table %s |
| Long Text: | Global indexes are defined on a table when direct path loading a single partition of the table. |
| Repair Text: | From Oracle doc: Remove the global index from the named table and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Column %s in table %s does not exist |
| Long Text: | Column specified in the loader control file does not exist. |
| Repair Text: | From Oracle doc: Make sure the column exists and that you have privileges on it. Correct the loader control file if it is wrong. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Column %s in table %s of type %s not supported by direct path |
| Long Text: | The specified column of SQL column type string is not supported by the direct path loader. |
| Repair Text: | From Oracle doc: If the column is NULLable, remove it from the control file description. Then it will be loaded as a NULL. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26020 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | index %s.%s loaded successfully with %s keys |
| Long Text: | Non-partitioned index information put to loader log file. |
| Repair Text: | From Oracle doc: No action required. This is an informational message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26021 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | index %s.%s partition %s loaded successfully with %s keys |
| Long Text: | Partitioned index information put to loader log file. |
| Repair Text: | From Oracle doc: No action required. This is an informational message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index %s.%s was made unusable due to: |
| Long Text: | A non-partitioned index was made index unusable due to the error displayed below this error. |
| Repair Text: | From Oracle doc: Depending on the error, either rebuild the index, or drop and re-create it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index %s.%s partition %s was made unusable due to: |
| Long Text: | A partition of a partitioned index was made index unusable due to error displayed below this error. |
| Repair Text: | From Oracle doc: Depending on the error, either rebuild the index partition, or drop and re-create the entire index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable |
| Long Text: | User requested SKIP_UNUSABLE_INDEXES option, and the index segment was in unusable state prior to the beginning of the load. |
| Repair Text: | From Oracle doc: Informational only. User will need to either rebuild the index or index partition, or re-create the index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SKIP_INDEX_MAINTENANCE option requested |
| Long Text: | A request was made that index maintenance be skipped on a direct path load. |
| Repair Text: | From Oracle doc: The listed index was put into Index Unusable state due to the user requesting that index maintenance be skipped. Either rebuild the index or index partitions, or drop and re-create the index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unique index %s.%s initially in unusable state |
| Long Text: | A unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES). |
| Repair Text: | From Oracle doc: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unique index %s.%s partition %s initially in unusable state |
| Long Text: | A partition of a unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES). |
| Repair Text: | From Oracle doc: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index %s.%s initially in unusable state |
| Long Text: | An index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader. |
| Repair Text: | From Oracle doc: Either rebuild the index, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index %s.%s partition %s initially in unusable state |
| Long Text: | A partition of an index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader. |
| Repair Text: | From Oracle doc: Either rebuild index partition, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index %s.%s had %s partitions made unusable due to: |
| Long Text: | A logical index error occurred on a partitioned index which affected one or more index partitions, which are listed below this message. |
| Repair Text: | From Oracle doc: The affected index partitions will have to be rebuilt, or, the entire index dropped and re-created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index maintenance error, the load cannot continue |
| Long Text: | A index error occurred during the index maintenance phase of a direct path load. The load cannot continue. See error message below this message. |
| Repair Text: | From Oracle doc: See action for the error message which follows this one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index %s.%s loading aborted after %s keys |
| Long Text: | An index error occurred during direct-load of an index-organized table. Loading had to be aborted. No rows were loaded. |
| Repair Text: | From Oracle doc: Check the key just following the number of keys mentioned above. This key caused the index problem mentioned in an earlier message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26033 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error while evaluating index %s.%s, row %s due to: |
| Long Text: | An index error occurred while attempting to evaluate an expression on a functional index. |
| Repair Text: | From Oracle doc: Verify that the input data is valid for the functional index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26034 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | end of logical record found when reading length of varying length field |
| Long Text: | While attempting to read the length portion of a varying length field, then end of the logical record was reached. |
| Repair Text: | From Oracle doc: Verify that the control file describes the data correctly and that the data in the datafile matches the description in the control file |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Record %s: Rejected - Error on table %s, subpartition %s |
| Long Text: | The record indicated caused an Oracle error on insert. |
| Repair Text: | From Oracle doc: Determine the Oracle error and correct the record. The offending column(s) are not known. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | subpartition load specified but table %s is not subpartitioned |
| Long Text: | The Loader control file contains a PARTITION clause but the table being loaded is not subpartitioned. |
| Repair Text: | From Oracle doc: Remove the subpartition specification from the SQL*Loader control file and retry the load. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Record %s: Rejected - Error on table %s, subpartition %s |
| Long Text: | The record indicated caused an Oracle error on insert. |
| Repair Text: | From Oracle doc: Determine the Oracle error and correct the record. The offending column(s) are not known. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error converting character length field to a number |
| Long Text: | An error occurred while attempting to convert the characters containing the count portion of a VARCHARC or VARRAWC field. |
| Repair Text: | From Oracle doc: Verify that the count portion for the field has the correct value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Table %s has domain index defined upon it |
| Long Text: | Direct path load was specified for a table which has a domain index defined upon it. |
| Repair Text: | From Oracle doc: Drop domain index(es) defined on the table or use the conventional path. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Data block was loaded using the NOLOGGING option |
| Long Text: | An attempt was made to access data in a block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option. |
| Repair Text: | From Oracle doc: Drop the object containing the block. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DATETIME/INTERVAL datatype conversion error |
| Long Text: | The column could not be converted from DATETIME datatype to internal DATETIME/CHARACTER datatype. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to convert format %s into internal form |
| Long Text: | An attempt to convert a DATETIME format string into internal format in preparation for DATETIME datatype processing failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to convert time zone for DATETIME/INTERVAL processing |
| Long Text: | An attempt to convert the time zone specified by the ORA_STDZ environment variable to internal format failed. |
| Repair Text: | From Oracle doc: Verify that the setting for ORA_STDZ is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to to get DATETIME/INTERVAL reference date |
| Long Text: | An attempt to retrieve the system reference date for DATETIME/INTERVAL datatypes failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is not part of database being loaded |
| Long Text: | A parallel load file was specified which is not part of the database. |
| Repair Text: | From Oracle doc: Check filename and pathname for correctness. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26079 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is not part of table %s.%s |
| Long Text: | A parallel load file was specified which is not in the tablespace of the table being loaded. |
| Repair Text: | From Oracle doc: Check to make sure that the specified parallel load file is in the tablespace of the table being loaded. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26080 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file %s is not part of table %s.%s partition %s |
| Long Text: | A parallel load file was specified which is not in the tablespace of the table (partition, subpartition) being loaded. When a partitioned table is being loaded, the file must be in the tablespace of every partition or subpartition (that is, each (sub)partition must be in the same tablespace). |
| Repair Text: | From Oracle doc: Specify a different parallel load file, or no file at all. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26081 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | load stream synchronization error |
| Long Text: | The row header flag byte contains an unexpected value, this indicates that an error has occurred in either the generation of, or the pushing of the load stream from the client to the server. |
| Repair Text: | From Oracle doc: Usually due to an application programming error when dealing with error handling, or not resetting the stream state. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | load of overlapping segments on table %s.%s is not allowed |
| Long Text: | Client application is attempting to do multiple direct path load operations on the same table, but the segments overlap. |
| Repair Text: | From Oracle doc: Check the partition names (subname attribute of the direct path context) being loaded. Make sure you are not loading a table and a partition of the same table. Make sure you are not loading a partition, and a sub-partition within the same partition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | direct path context already finished |
| Long Text: | An OCIDirPathLoadStream operation was attempted after OCIDirPathFinish was called. Once a direct path operation has been finished, no more data can be loaded. |
| Repair Text: | From Oracle doc: Check program logic to make sure OCIDirPathLoadStream is not called after OCIDirPathFinish. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26085 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | direct path operation must start its own transaction |
| Long Text: | A direct path operation is being attempted within a transaction that has already been started. |
| Repair Text: | From Oracle doc: Commit the transaction and Prepare the direct path operation again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26086 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | direct path does not support triggers |
| Long Text: | A direct path operation is being attempted on a table which has enabled triggers. |
| Repair Text: | From Oracle doc: Disable the triggers on the table and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26087 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | direct path does not support referential or check constraints |
| Long Text: | A direct path operation is being attempted on a table which has enabled referential integrity or enabled check constraints. |
| Repair Text: | From Oracle doc: Disable the referential integrity and/or check constraints on the table and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26088 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scalar column '%s' must be specified prior to LOB columns |
| Long Text: | All scalar columns (that is, non-LOB and non-LONG columns) must be specified by the client of the direct path API prior to specifying any LOB columns. |
| Repair Text: | From Oracle doc: Specify all scalar columns prior to specifying any LOB columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26089 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | LONG column '%s' must be specified last |
| Long Text: | A client of the direct path API specified a LONG column to be loaded, but the LONG column was not the last column to be specified. |
| Repair Text: | From Oracle doc: Specify the LONG column last. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26090 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | row is in partial state |
| Long Text: | A direct path operation is being finished or a data save request has been made, but the table for which the request is being made on has a row in partial state. The row must be completed before the segment high water marks can be moved. |
| Repair Text: | From Oracle doc: Either complete the row, or abort the direct path operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26091 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | requested direct path operation not supported |
| Long Text: | A direct path operation was requested that is not supported |
| Repair Text: | From Oracle doc: Do not use that operation. Currently, UNLOAD is not supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26092 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | only LONG or LOB types can be partial |
| Long Text: | A column which is not a LONG or LOB had the OCI_DIRPATH_COL_PARTIAL flag associated with it. Only LONG or LOB type columns can be loaded in pieces. |
| Repair Text: | From Oracle doc: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26093 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | stream offset does not map to a column array |
| Long Text: | The ROW_COUNT attribute was being read from a direct path stream handle and it was found that the stream offset for the last processed row did not map to a column array offset. |
| Repair Text: | From Oracle doc: Make sure the stream was sourced from a column array. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26094 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | stream format error: input column overflow |
| Long Text: | An input stream contained data for more input columns than specified by the client of the direct path API. |
| Repair Text: | From Oracle doc: Make sure that the stream being loaded is for the correct table. Check initialization sequence. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26095 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unprocessed stream data exists |
| Long Text: | Either a OCIDirPathLoadStream call was made which provided more stream data prior to the server being able to fully process the stream data that it already has, or a OCIDirPathFinish call was made when the server had unprocessed stream data. |
| Repair Text: | From Oracle doc: Most likely an application misuse of the direct path API. Make sure that the stream is not being reset inadvertently prior to any previous stream data being processed, or, that OCIDirPathFinish is not being called prematurely (that is, stream pushed, error encountered and LoadStream not called to process the remainder of the stream before Finish is called). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26096 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | transfer size too small for row data (number bytes required) |
| Long Text: | Either the transfer buffer size specified, or the default transfer buffer size (if you did not specify a size), is too small to contain a single row of the converted row data. |
| Repair Text: | From Oracle doc: Set the transfer buffer size attribute of the direct path context to be larger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26097 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported conversion for column %s (from type number to type number) |
| Long Text: | The direct path API does not support the required conversion. |
| Repair Text: | From Oracle doc: Make sure the types are correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26098 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | direct path context is not prepared |
| Long Text: | A direct path API function was called with a direct path context which has not been prepared. |
| Repair Text: | From Oracle doc: Make sure all necessary attributes in the direct path context have been set, and the context is prepared via OCIDirPathPrepare. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26099 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | direct path context is already prepared |
| Long Text: | OCIDirPathPrepare was called with a context that has already been prepared. |
| Repair Text: | From Oracle doc: Free the direct path context, set necessary attributes, and call OCIDirPathPrepare. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26100 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | unused error |
| Long Text: | This error is not used. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace # in file header is %s rather than %s for file %s |
| Long Text: | The tablespace number in the file header is inconsistent with that in the control file. |
| Repair Text: | From Oracle doc: Check if the control file has been migrated correctly. Retry with the correct control file and datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | relative file # in file header is %s rather than %s for file %s |
| Long Text: | The relative file number in the file header is inconsistent with that in the control file. |
| Repair Text: | From Oracle doc: Check if the control file has been migrated correctly. Retry with the correct control file and datafile. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | V6 or V7 data file used to create control file |
| Long Text: | The file header of the referenced file is in V6 or V7 format. |
| Repair Text: | From Oracle doc: Either remove the file from the create control file command, or somehow migrate the file header to V8 format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error on caching "%s"."%s" |
| Long Text: | Attempt to cache the replication information which is unavailable in the catalog for the object. |
| Repair Text: | From Oracle doc: Use DBMS_REPUTIL.SYNC_UP_REP to validate the replication catalog, or use DBMS_REPUTIL.MAKE_INTERNAL_PKG to validate internal package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | RepAPI operation failure |
| Long Text: | An external RepAPI operation failed. |
| Repair Text: | From Oracle doc: Consult detail error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error resignal |
| Long Text: | An internal service failed and signalled an error. |
| Repair Text: | From Oracle doc: Consult detail error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal RepAPI operation failure on object %s.%s |
| Long Text: | An unexpected internal RepAPI failure was detected. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operation not implemented |
| Long Text: | The caller requested a RepAPI operation that was not implemented. |
| Repair Text: | From Oracle doc: Do not issue this call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unexpected internal null |
| Long Text: | An internal buffer control structure was NULL. |
| Repair Text: | From Oracle doc: Verify that sufficient memory resources are available to RepAPI. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null global context |
| Long Text: | An internal buffer control structure was NULL. |
| Repair Text: | From Oracle doc: Verify that sufficient memory resources are available to RepAPI. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null master connection |
| Long Text: | The master connection handle was or became invalid. |
| Repair Text: | From Oracle doc: Verify that the master connection is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null snapshot connection |
| Long Text: | The client connection handle was or became invalid. |
| Repair Text: | From Oracle doc: Verify that the client connection is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null snapshot control structure |
| Long Text: | An internal snapshot control structure could not be obtained. |
| Repair Text: | From Oracle doc: Check that the owner and users provided are correct. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot name: '%s' is greater than max. allowed length of %s bytes |
| Long Text: | The specified snapshot name was too long. |
| Repair Text: | From Oracle doc: Shorten the snapshot name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | master table '%s.%s' not found |
| Long Text: | A RepAPI operation was attempted against a non-existent or invalid master table. |
| Repair Text: | From Oracle doc: Verify that the master table object exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error pushing transaction to def$error |
| Long Text: | An unexpected error occurred while sending an DEF$ERROR RPC to the master site. |
| Repair Text: | From Oracle doc: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact the local or master site administrator, if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | push error: master proc. %s$RP.%s failed for trans:%s seq:%s |
| Long Text: | A conflict/error occurred at the master site while executing a $RP.rep_insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master. |
| Repair Text: | From Oracle doc: Notify master site system administrator or database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object '%s.%s' not found |
| Long Text: | The specified object was expected but not found. |
| Repair Text: | From Oracle doc: Verify that the specified object exists and is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26515 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no master log available for '%s.%s' |
| Long Text: | The specified master log was not found or available for the named table. |
| Repair Text: | From Oracle doc: Create the master log at the master site or correct any problems that may exist with the log. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26516 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no push transaction acknowledgement |
| Long Text: | RepAPI was unable to confirm that the last pushed transaction was successfully committed by the master site. |
| Repair Text: | From Oracle doc: Verify that the communications link between the local site and the master site is still valid. If the transaction has not been committed at the master, repush the transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26517 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot control entry for '%s.%s' was not found |
| Long Text: | The specified snapshot catalog control record was not found. |
| Repair Text: | From Oracle doc: Verify that the local snapshot catalog is valid and that the local snapshot is properly defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26518 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | push queue synchronization error detected |
| Long Text: | Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism. |
| Repair Text: | From Oracle doc: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable snapshot logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26519 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no memory available to allocate |
| Long Text: | There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area. |
| Repair Text: | From Oracle doc: Shut down one or more local applications to attempt to free heap memory and retry the RepAPI operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26520 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal memory failure |
| Long Text: | An internal memory error was detected. |
| Repair Text: | From Oracle doc: Check if other errors have occurred or determine if any local application may have corrupted the memory subsystem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26521 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rpc initialization error |
| Long Text: | An error occurred during the initialization of a PL/SQL RPC. |
| Repair Text: | From Oracle doc: Verify that the procedure to be invoked exists and is valid at the master site and is executable by the RepAPI user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26522 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rpc execution error |
| Long Text: | An error occurred during the execution of a PL/SQL RPC. |
| Repair Text: | From Oracle doc: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked RPC. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26523 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | rpc termination error |
| Long Text: | An error occurred during the termination of a PL/SQL RPC. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory. |
| Repair Text: | From Oracle doc: Fix any server side problems first, determine if the RepAPI memory subsystem has been corrupted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26524 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | nls subsystem initialization failure for product=%s, facility=%s |
| Long Text: | The NLS product/facility error message file could not be located or properly initialized. |
| Repair Text: | From Oracle doc: Check that the error message directory and file(s) have been properly installed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26525 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session connection attempt failed for %s (@%s) |
| Long Text: | A connection could not be established to the specified database using the provided connection string. |
| Repair Text: | From Oracle doc: Check that the user, password, connect string, names services, network, and any remote site listener process are properly installed and working. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26526 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | snapshot sql ddl parse/expansion failed for %s.%s |
| Long Text: | The client SQL snapshot definition query could not be properly parsed by the master Oracle site. |
| Repair Text: | From Oracle doc: Check that snapshot DDL SQL is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26527 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | local store callback init phase failed for '%s.%s' |
| Long Text: | The client callback failed during its INIT phase for the named object. |
| Repair Text: | From Oracle doc: Verify that the objects referenced by the client callback exist and are valid. Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26528 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | local store callback proc phase failed for '%s.%s' |
| Long Text: | The client callback failed during its PROC phase for the named object. |
| Repair Text: | From Oracle doc: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26529 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | local store callback term phase failed for '%s.%s' |
| Long Text: | The client callback failed during its TERM phase for the named object. |
| Repair Text: | From Oracle doc: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26530 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to build snapshot refresh control list |
| Long Text: | The snapshot control list could not be constructed. This is generally the result of an error while accessing the local snapshot catalog. |
| Repair Text: | From Oracle doc: Verify that the named snapshot(s) are properly defined and valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26532 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | replication parallel push simulated site failure |
| Long Text: | A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site. |
| Repair Text: | From Oracle doc: Do not enable the event for normal operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | collision: tranID number ignored and purged |
| Long Text: | A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site. |
| Repair Text: | From Oracle doc: See the action section for E_QUEUESYNC (26518). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26535 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number byte row cache insufficient for table with rowsize=number |
| Long Text: | A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site. |
| Repair Text: | From Oracle doc: Increase the RepAPI row buffer size or reduce the width of the replicated tables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26536 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh was aborted because of conflicts caused by deferred transactions |
| Long Text: | There are outstanding conflicts logged in the DEFERROR table at the snapshot's master site. |
| Repair Text: | From Oracle doc: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result in an updatable snapshot's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26563 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | renaming this table is not allowed |
| Long Text: | Attempt to rename a replicated table, an updatable snapshot table or the master table of a snapshot for which a snapshot log has been created. |
| Repair Text: | From Oracle doc: If desired, unregister the replicated table with DBMS_REPCAT.DROP_MASTER_REPOBJECT, or use the recommended procedure to rename the master table of a snapshot. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26564 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s argument is not of specified type |
| Long Text: | User passed type of the given argument number does not match with the type of the argument in the stored arguments. |
| Repair Text: | From Oracle doc: Invoke correct type procedure (that is, get_XXX_arg). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26565 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Call to type_arg made before calling dbms_defer.call |
| Long Text: | User invoked type_arg procedure before starting a deferred call. |
| Repair Text: | From Oracle doc: Invoke various procedures in the correct order. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26566 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Couldn't open connect to %s |
| Long Text: | Failed to open connection using given database link. |
| Repair Text: | From Oracle doc: Make sure that the database link is valid and remote m/c is up. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26571 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s.%s.%s: number of arguments (%s) does not match replication catalog |
| Long Text: | The number of arguments does not match the replication catalog. |
| Repair Text: | From Oracle doc: Examine the total number of arguments for the RPC call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26572 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s.%s.%s: argument %s does not match replication catalog |
| Long Text: | The (RPC) call is corrupted. |
| Repair Text: | From Oracle doc: Examine total number of arguments and each argument for the RPC call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-26575 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | remote database does not support replication parallel propagation |
| Long Text: | The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation. |
| Repair Text: | From Oracle doc: Use serial propagation or upgrade the remote database to Oracle 8.0 or above. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqsbi: failed to initialize storage subsystem (SBT) layer |
| Long Text: | SBTINIT returned an error, additional information indicates error. |
| Repair Text: | From Oracle doc: Verify that vendor's storage subsystem product is operating correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported device type |
| Long Text: | The specified device type is supported on this platform. |
| Repair Text: | From Oracle doc: Check V$BACKUP_DEVICE for supported device types. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function called with invalid device structure |
| Long Text: | An internal error occurred. Additional information indicates which function encountered error. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot open file on device allocated with NOIO option |
| Long Text: | An internal error occurred. A file is being created/retrieved on a device allocated with NOIO option, additional information indicates which function encountered error. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid blocksize specified |
| Long Text: | An internal error occurred. The block size specified is incorrect for the device on which file is being created, additional information indicates block size specified, and the function that encountered the error. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot open file for async I/O on device not supporting async |
| Long Text: | An internal error occurred. A file is being opened for asynchronous I/O on a device that does not support asynchronous I/O, additional information indicates which function encountered error. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sbtremove returned error |
| Long Text: | Additional information indicates error returned by SBTREMOVE, and the function that encountered the error. |
| Repair Text: | From Oracle doc: Verify that the vendor's storage subsystem product is operating correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to open file |
| Long Text: | SBTOPEN returned error, additional information indicates error returned from SBTOPEN, and the function that encountered the error. |
| Repair Text: | From Oracle doc: Verify that the vendor's storage subsystem product is operating correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function called with invalid file structure |
| Long Text: | An internal error occurred. Additional information indicates which function encountered error. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfwrt: cannot write to file opened for read |
| Long Text: | An internal error occurred. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfwrt: write to file failed |
| Long Text: | SBTWRITE returned error, additional information indicates error returned from SBTWRITE. |
| Repair Text: | From Oracle doc: Verify that the vendor's storage subsystem product is operating correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27011 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrd: cannot read from file opened for write |
| Long Text: | An internal error occurred. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27012 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrd: read from file failed |
| Long Text: | SBTREAD returned error, additional information indicates error returned from SBTREAD. |
| Repair Text: | From Oracle doc: Verify that the vendor's storage subsystem product is operating correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27013 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqdel: cannot delete an open file |
| Long Text: | An internal error occurred. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27014 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqpini: translation error while expanding SS_UDMPDIR |
| Long Text: | Failure of SLTLN in SKGFQPINI. |
| Repair Text: | From Oracle doc: Check additional return error for more information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27015 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfcls: failed to close the file |
| Long Text: | SBTCLOSE returned an error. Additional information indicates error returned from SBTCLOSE. |
| Repair Text: | From Oracle doc: Verify that the vendor's storage subsystem product is operating correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27016 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfcls: sbtinfo returned error |
| Long Text: | Additional information indicates error returned from SBTINFO. |
| Repair Text: | From Oracle doc: Verify that the vendor's storage subsystem product is operating correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27017 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH) |
| Long Text: | Media handle string length exceeds SSTMXQMH. |
| Repair Text: | From Oracle doc: Verify that the vendor's storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is at least 64 (the limit specified for SBTINFO). additional information indicates the media handle string length returned by SBTINFO, and the limit (SSTMXQMH). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27018 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | BLKSIZE is not a multiple of the minimum physical block size |
| Long Text: | User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform. |
| Repair Text: | From Oracle doc: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27019 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tape filename length exceeds limit (SBTOPMXF) |
| Long Text: | The length of the tape file name provided to sequential I/O OSD functions is too long. |
| Repair Text: | From Oracle doc: Additional information indicates in which function this error is encountered, the length of file name provided, and the limit on file name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | named devices not supported |
| Long Text: | The platform or the specified device type does not support named devices. |
| Repair Text: | From Oracle doc: Do not specify device name or use a device type that supports named devices. Use V$BACKUP_DEVICE view to see what device types and names (if any) are available. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sequential file handle must be specified |
| Long Text: | The file name which will be passed to SBTOPEN was not specified. |
| Repair Text: | From Oracle doc: Specify a file name and continue. If this is a backup set being created via Recovery Manager, use the 'format' option to specify the backup piece handle name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqsbi: could not allocate memory for media manager |
| Long Text: | Oracle could not allocate memory required by the media management software which is linked with Oracle to provide backup/restore services. |
| Repair Text: | From Oracle doc: Increase the amount of memory available to the Oracle process and retry the backup/restore. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqsbi: media manager protocol error |
| Long Text: | The media management software which is linked with Oracle to provide backup/restore services did not provide its function pointer structure to Oracle. This is an internal error in the media management product. |
| Repair Text: | From Oracle doc: Contact the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqsbi: sbtinit2 returned error |
| Long Text: | SBTINIT2 returned an error. This happens during a backup or restore operation. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqsbi: invalid media manager context area size |
| Long Text: | The media management software requested a context area size which is greater than the maximum allowable size. This is an internal error in the media management product. |
| Repair Text: | From Oracle doc: Contact the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrls: sbtend returned error |
| Long Text: | SBTEND returned an error. This happens during a backup or restore operation. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sbtremove2 returned error |
| Long Text: | SBTREMOVE2 returned an error. This happens when deleting a backup file. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqcre: sbtbackup returned error |
| Long Text: | SBTBACKUP returned an error. This happens when creating a backup file during a backup operation. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrtrv: sbtrestore returned error |
| Long Text: | SBTRESTORE returned an error. This happens when retrieving a backup file during a restore operation. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfwrt: sbtwrite2 returned error |
| Long Text: | SBTWRITE2 returned an error. This happens while writing a backup file during a backup operation. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27031 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | mirror resilvering functions not supported |
| Long Text: | An internal error occurred. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27032 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrpini: failed to obtain file size limit |
| Long Text: | GETRLIMIT system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27033 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrpini: failed to obtain file size limit |
| Long Text: | ULIMIT system call returned an error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27034 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrcre: maximum length of ORACLE_SID exceeded |
| Long Text: | Too many characters in the ORACLE_SID string. |
| Repair Text: | From Oracle doc: Rename the ORACLE_SID to a string of up to the maximum number of characters specified for your system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | logical block size is invalid |
| Long Text: | Logical block size for Oracle files must be a multiple of the physical block size, and less than the maximum. |
| Repair Text: | From Oracle doc: Block size specified is returned as additional information, check initialization parameters, additional information also indicates which function encountered the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27036 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | translation error, unable to expand file name |
| Long Text: | Additional information indicates SLTLN/SLNRM error, and also indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check additional information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27037 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to obtain file status |
| Long Text: | STAT system call returned an error, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27038 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrcre: file exists |
| Long Text: | Trying to create a database file, but file by that name already exists. |
| Repair Text: | From Oracle doc: Verify that name is correct, specify reuse if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27039 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | create file failed, file size limit reached |
| Long Text: | An attempt was made to create a file that exceeds the process' file size limit, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Raise the file size limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27040 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrcre: create error, unable to create file |
| Long Text: | Create system call returned an error, unable to create file. |
| Repair Text: | From Oracle doc: Verify the file name and permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27041 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to open file |
| Long Text: | Open system call returned an error, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27042 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | not enough space on raw partition to fullfill request |
| Long Text: | This is an internal error. The file is too large for the raw partition. Additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check for trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27043 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to seek to beginning of file |
| Long Text: | Seek system call failed, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27044 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to write the header block of file |
| Long Text: | Write system call failed, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27045 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to close the file |
| Long Text: | Close system call failed, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27046 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | file size is not a multiple of logical block size |
| Long Text: | File size as indicated by STAT is not correct, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Verify that the file has not been overwritten or truncated. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27047 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to read the header block of file |
| Long Text: | Read system call failed, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27048 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfifi: file header information is invalid |
| Long Text: | Possibly trying to use a non-database file as a database file. |
| Repair Text: | From Oracle doc: Verify that file is a database file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27049 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to seek to and read the last block |
| Long Text: | An attempt was made to seek to and read the last block in file, additional information indicates which function encountered error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27050 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function called with invalid FIB/IOV structure |
| Long Text: | This is an internal error. Additional information indicates which function encountered error. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27052 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to flush file data |
| Long Text: | FSYNC system call returned error, additional information indicates which function encountered the error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27053 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfifi: blocksize in file header not a multiple of logical block size |
| Long Text: | The logical block size is invalid, additional information indicates the logical block size and the block size in the file header. |
| Repair Text: | From Oracle doc: Use a different logical block size, or do not reuse file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27056 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrdel: could not delete file |
| Long Text: | Unlink system call returned error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27057 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfask: cannot perform async I/O to file |
| Long Text: | This is an internal error. The query is being asked about asynchronous vector I/O when the file does not support asynchronous I/O. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27058 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfask: question parameter is invalid |
| Long Text: | This is an internal error. An invalid query is being asked. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27059 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrsz: could not reduce file size |
| Long Text: | FTRUNCATE system call returned error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27060 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfofi: could not set close-on-exec bit on file |
| Long Text: | FCNTL system call returned error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27061 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfospo: waiting for async I/Os failed |
| Long Text: | AIOWAIT function returned error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27062 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfospo: could not find pending async I/Os |
| Long Text: | This is an internal error. There should have been some asynchronous I/Os in the system but a blocking AIOWAIT indicates that there are no more I/Os. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27063 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfospo: number of bytes read/written is incorrect |
| Long Text: | The number of bytes read/written as returned by AIOWAIT does not match the original number, additional information indicates both these numbers. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27064 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: cannot perform async I/O to file |
| Long Text: | This is an internal error. A request was made to perform asynchronous I/O when IOV indicates that it cannot be performed on the file. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27065 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: cannot perform async vector I/O to file |
| Long Text: | This is an internal error. A request was made to perform asynchronous vector I/O when it cannot be performed on the file. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27066 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: number of buffers in vector I/O exceeds maximum |
| Long Text: | This is an internal error. The number of buffers in vector I/O exceeds maximum allowed by the OSD, additional information indicates both these numbers. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27067 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: size of buffer is invalid |
| Long Text: | This is an internal error. The buffer size is either 0, or greater than SSTIOMAX or not a multiple of logical block size, additional information indicates where in function the error was encountered and the buffer size. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27068 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: buffer is not aligned properly |
| Long Text: | This is an internal error. The buffer is not aligned to SSIOALIGN boundary, additional information indicates where in function the error was encountered and the buffer pointer. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27069 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: attempt to do I/O beyond the range of the file |
| Long Text: | This is an internal error. The range of blocks being read or written is outside the range of the file, additional information indicates the starting block number, number of blocks in I/O, and the last valid block in the file. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27070 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: async read/write failed |
| Long Text: | AIOREAD/AIOWRITE system call returned error, additional information indicates starting block number of I/O. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: unable to seek to desired position in file |
| Long Text: | LSEEK system call returned error, additional information indicates block number in file to which seek was attempted. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27072 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdisp: I/O error |
| Long Text: | READ/WRITE/READV/WRITEV system call returned error, additional information indicates starting block number of I/O. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27073 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfcfi: async I/Os remaining to be dequeued for this file |
| Long Text: | This is an internal error. The file is being closed but not all asynchronous I/Os to the file have been dequeued, additional information indicates number of I/Os pending on the file. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrofl: unable to determine limit for open files |
| Long Text: | GETRLIMIT system call returned error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27075 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrofl: SSTMOFRC constant too large |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27076 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrofl: unable to set limit for open files |
| Long Text: | SETRLIMIT system call returned error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27077 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfofi: too many files open |
| Long Text: | This is an internal error. The number of files opened through SKGFOFI has reached the limit. |
| Repair Text: | From Oracle doc: Check for a trace file and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqio: unable to get/set file status flags |
| Long Text: | System call FCNTL with F_GETFL/F_SETFL flag returned error. |
| Repair Text: | From Oracle doc: Check errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27086 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfglk: unable to lock file - already in use |
| Long Text: | The file is locked by another process, indicating that it is currently in use by a database instance. |
| Repair Text: | From Oracle doc: Determine which database instance legitimately owns this file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27087 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfglk: unable to get share lock - file not readable |
| Long Text: | Share lock request was made on a file not open for read access. |
| Repair Text: | From Oracle doc: File must be open read-only or read-write to get a share lock. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27088 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfglk: unable to get file status |
| Long Text: | The file is not open or the file descriptor is invalid. |
| Repair Text: | From Oracle doc: Make sure the file is open and the descriptor is valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27089 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrlk: unable to release advisory lock |
| Long Text: | The file lock release failed. |
| Repair Text: | From Oracle doc: See the errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27091 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfqio: unable to queue I/O |
| Long Text: | A read/write/readv/writev system call returned error. Additional information indicates the starting block number of the I/O. |
| Repair Text: | From Oracle doc: Check the errno. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | shared memory realm already exists |
| Long Text: | An attempt was made to start duplicate instances, or tried to restart an instance that had not been properly shut down. |
| Repair Text: | From Oracle doc: Use a different instance name, or cleanup the failed instance's SGA. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | shared memory realm does not exist |
| Long Text: | Unable to locate shared memory realm. |
| Repair Text: | From Oracle doc: Verify that the realm is accessible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | out of memory |
| Long Text: | Out of memory. |
| Repair Text: | From Oracle doc: Consult the trace file for details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to removed shared memory segment |
| Long Text: | SHMCTL() call failed. |
| Repair Text: | From Oracle doc: check permissions on segment, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to determine size of shared memory segment |
| Long Text: | SHMCTL() call failed. |
| Repair Text: | From Oracle doc: check permissions on segment, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to protect memory |
| Long Text: | MPROTECT() call failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to attach to shared memory segment |
| Long Text: | SHMAT() call failed. |
| Repair Text: | From Oracle doc: Check permissions on segment, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to detach from shared memory segment |
| Long Text: | SHMDT() call failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27125 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to create shared memory segment |
| Long Text: | SHMGET() call failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27126 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to lock shared memory segment in core |
| Long Text: | Insufficient privileges to lock shared memory segment in core. |
| Repair Text: | From Oracle doc: Make sure the process is running with the necessary privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27127 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to unlock shared memory segment |
| Long Text: | Insufficient privileges to unlock shared memory segment. |
| Repair Text: | From Oracle doc: Make sure the process is running with the necessary privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27128 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to determine pagesize |
| Long Text: | SYSCONF() call failed. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27141 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid process ID |
| Long Text: | Process operation attempted using invalid process ID. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27142 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not create new process |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and if possible increase the number of processes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27143 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OS system call failure |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27144 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to kill process failed |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27145 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient resources for requested number of processes |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27146 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | post/wait initialization failed |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27147 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | post/wait reset failed |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27148 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | spawn wait error |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27149 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | assignment out of range |
| Long Text: | This is an internal error. A request was made for a conversion too large for the type. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to notify process of pending oradebug call failed |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | buffer not large enough to hold process ID %s |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to post process failed |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wait operation failed |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27154 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | post/wait create failed |
| Long Text: | This is an internal error. Multiple post/wait creates were attempted simultaneously. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not execute file |
| Long Text: | Operating system call failed. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27156 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | request for process information failed |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27190 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfrd: sbtread2 returned error |
| Long Text: | SBTREAD returned an error. This happens while reading a backup file during a restore operation. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27191 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sbtinfo2 returned error |
| Long Text: | SBTINFO2 returned an error. This happens while retrieving backup file information from the media manager's catalog. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27192 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfcls: sbtclose2 returned error - failed to close file |
| Long Text: | SBTCLOSE2 returned an error. This happens while closing a backup file during a backup or restore operation. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27193 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sbtinfo2 did not return volume label |
| Long Text: | SBTINFO2 did not return the volume label information for the backup file that was just created. This is an internal error in the media management product. |
| Repair Text: | From Oracle doc: Contact the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27194 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfdvcmd: sbtcommand returned error |
| Long Text: | SBTCOMMAND returned an error. This happens when an RMAN SEND command is issued. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27195 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | proxy copy not supported |
| Long Text: | An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy. |
| Repair Text: | From Oracle doc: Rerun the backup in non-proxy mode, or contact the media management vendor if the software is supposed to support proxy copy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27196 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpbk: sbtpcbackup returned error |
| Long Text: | SBTPCBACKUP returned an error. This happens when a proxy backup is begun. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27197 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfprs: sbtpcrestore returned error |
| Long Text: | SBTPCRESTORE returned an error. This happens when a proxy restore is begun. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27198 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpvl: sbtpcvalidate returned error |
| Long Text: | SBTPCVALIDATE returned an error. This happens during a proxy backup or restore. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27199 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpst: sbtpcstatus returned error |
| Long Text: | SBTPCSTATUS returned an error. This happens during a proxy backup or restore. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpgo: sbtpcstart returned error |
| Long Text: | SBTPCSTART returned an error. This happens during a proxy backup or restore. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpcm: sbtpccommit returned error |
| Long Text: | SBTPCCOMMIT returned an error. This happens during a proxy backup or restore. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpen: sbtpcend returned error |
| Long Text: | SBTPCEND returned an error. This happens during a proxy backup or restore. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpqb: sbtpcquerybackup returned error |
| Long Text: | SBTPCQUERYBACKUP returned an error. This happens during a proxy backup. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27204 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpqr: sbtpcqueryrestore returned error |
| Long Text: | SBTPCQUERYRESTORE returned an error. This happens during a proxy restore. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27205 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | skgfpcn: sbtpccancel returned error |
| Long Text: | SBTPCCANCEL returned an error. This happens during a proxy restore. |
| Repair Text: | From Oracle doc: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27206 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | requested file not found in media management catalog |
| Long Text: | A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog. |
| Repair Text: | From Oracle doc: Retry the command with a different file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27207 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in device PARMS - parentheses mismatch or missing |
| Long Text: | User-supplied PARMS value has incorrect syntax. |
| Repair Text: | From Oracle doc: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27208 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in device PARMS - environment variable value missing |
| Long Text: | User-supplied PARMS value has incorrect syntax. |
| Repair Text: | From Oracle doc: Retry the command with the correct syntax: ENV=(var1=val1,var2=val2,..) |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27209 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in device PARMS - unknown keyword or missing = |
| Long Text: | User-supplied PARMS value has incorrect syntax. The server expected to find ENV or BLKSIZE, but found an unknown keyword. |
| Repair Text: | From Oracle doc: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27210 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error in device PARMS |
| Long Text: | User-supplied PARMS value has incorrect syntax. |
| Repair Text: | From Oracle doc: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OS system dependent operation:%s failed with status: %s |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OS failure message: %s |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failure occurred at: %s |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | additional information: %s |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inter-instance IPC error |
| Long Text: | Most likely operating system call error. |
| Repair Text: | From Oracle doc: Check extra information and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error creating a port |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error setting up signal handler |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error querying network address of a port |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error destroying a port |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error connecting to a port |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error disconnecting from a port |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error sending a message |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error receiving a message |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error waiting for a request to complete |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC error posting a process |
| Long Text: | Operating system call error. |
| Repair Text: | From Oracle doc: Check errno and contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27528 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot allocate communication buffers of zero size |
| Long Text: | Client is trying to allocate a zero length message. |
| Repair Text: | From Oracle doc: Refer to KGXP.H for usage of KGXPVALO(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27529 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot allocate zero sized communication buffers |
| Long Text: | Client is trying to allocate a zero length message. |
| Repair Text: | From Oracle doc: Refer to KGXP.H for usage of KGXPVALO(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27530 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot deallocate pointer to NULL memory |
| Long Text: | Client is passing in a NULL pointer for deallocation. |
| Repair Text: | From Oracle doc: Refer to KGXP.H for usage of KGXPVFRE(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27531 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot destroy invalid port |
| Long Text: | The port is invalid. |
| Repair Text: | From Oracle doc: Re-create the port. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27532 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IPC global name service is not supported |
| Long Text: | The global name service used by KGXP is not supported. |
| Repair Text: | From Oracle doc: Either use a different name service, of abort the current process/thread. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27533 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trying to destroy invalid connection identifier |
| Long Text: | The connection identifier passed in is invalid. |
| Repair Text: | From Oracle doc: Check the connection identifier, or abort the process/thread. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot send unaligned message |
| Long Text: | The message being sent is not aligned on the required boundaries. |
| Repair Text: | From Oracle doc: Use the KGXPALSZ() macro to get the alignment size of messages, and align all messages on this boundary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27535 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exceeded the maximum vectored message size |
| Long Text: | An attempt was made to send a vectored message that exceeds the maximum vector size. |
| Repair Text: | From Oracle doc: Use a smaller vector size. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27536 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | multicast message is not aligned on the correct boundary |
| Long Text: | The message to multicast is not aligned on the proper boundary. |
| Repair Text: | From Oracle doc: Align the message appropriately. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27537 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot receive messages into unaligned buffers |
| Long Text: | The message being posted for receive is not aligned on the required boundary. |
| Repair Text: | From Oracle doc: Use the KGXPALSZ() macro to get the alignment size of messages, and align all messages on this boundary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27538 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to added accept handle to the free pool |
| Long Text: | Could not add an accept handle to the free pool. |
| Repair Text: | From Oracle doc: Exit the process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27539 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | accept handle free pool is empty. Cannot accept new connections |
| Long Text: | The free pool of accept handles is empty. |
| Repair Text: | From Oracle doc: Add accept handles to the free pool. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27540 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no more communication channels can be created for process/thread. already at maximum. |
| Long Text: | The maximum communication channels are already in use for this process/thread. |
| Repair Text: | From Oracle doc: Destroy connections which are not needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27541 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | fatal error trying to connect to remote port |
| Long Text: | Either the remote address is not valid, or the process is in bad shape. |
| Repair Text: | From Oracle doc: Destroy all connections, and try to re-establish them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27542 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed trying to queue up accept handles |
| Long Text: | The OSD would not allow KGXP to queue up the storage necessary to accept new incoming connections. |
| Repair Text: | From Oracle doc: Check the parameters; if they are okay, abort the process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27543 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot cancel an outstanding request |
| Long Text: | The OSD cannot cancel an outstanding request immediately. |
| Repair Text: | From Oracle doc: Shut down all connections and abort the process. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-27544 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | memory mapped communication is not supported |
| Long Text: | The platform does not support memory communication. |
| Repair Text: | From Oracle doc: Use the default send/receive. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28000 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | the account is locked |
| Long Text: | The user has entered wrong password consequently for maximum number of times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the database administrator has locked the account. |
| Repair Text: | From Oracle doc: Wait for PASSWORD_LOCK_TIME or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the password has expired |
| Long Text: | The user's account has expired and the password needs to be changed. |
| Repair Text: | From Oracle doc: Change the password or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28002 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the password will expire within %s days |
| Long Text: | The user's account is about to about to expire and the password needs to be changed. |
| Repair Text: | From Oracle doc: Change the password or contact the database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | password verification for the specified password failed |
| Long Text: | The new password did not meet the necessary complexity specifications and the PASSWORD_VERIFY_FUNCTION failed. |
| Repair Text: | From Oracle doc: Enter a different password. Contact the database administrator to find out the rules for choosing the new password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28004 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid argument for function specified in PASSWORD_VERIFY_FUNCTION %s |
| Long Text: | The password verification function does not have the required number and type of input/output arguments and/or the return argument. |
| Repair Text: | From Oracle doc: Check the Oracle Security Server Guide to find out the format of the password verification function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28005 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid logon flags |
| Long Text: | The flags are not properly set or conflicting flags are set in making calls. |
| Repair Text: | From Oracle doc: Call the function with appropriate flags set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28006 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | conflicting values for parameters %s and %s |
| Long Text: | The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot both be set. One parameter should be unlimited while other is set. |
| Repair Text: | From Oracle doc: Set one value to UNLIMITED explicitly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28007 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the password cannot be reused |
| Long Text: | The password cannot be reused for the specified number of days or for the specified number of password changes. |
| Repair Text: | From Oracle doc: Try the password that you have not used for the specified number of days or the specified number of password changes Refer to the password parameters in the CREATE PROFILE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28008 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid old password |
| Long Text: | Old password supplied is wrong; Hence user cannot be authenticated using old password. |
| Repair Text: | From Oracle doc: Supply the correct old password for authentication. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28009 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection to sys should be as sysdba or sysoper |
| Long Text: | Connect sys/password is no longer a valid syntax. |
| Repair Text: | From Oracle doc: Try connect sys/password as sysdba or connect sys/password as sysoper. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28010 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot expire external or global accounts |
| Long Text: | If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED GLOBALLY, this account cannot be expired. |
| Repair Text: | From Oracle doc: Try to expire the password of the user that has database password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28020 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IDENTIFIED GLOBALLY already specified |
| Long Text: | The IDENTIFIED GLOBALLY clause was specified twice. |
| Repair Text: | From Oracle doc: Use only one IDENTIFIED GLOBALLY clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28021 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot grant global roles |
| Long Text: | A role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain. |
| Repair Text: | From Oracle doc: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY to other, such as IDENTIFIED BY password), or allocate it to a global user via the central authority. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28022 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot grant external roles to global user or role |
| Long Text: | A role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users or global roles. |
| Repair Text: | From Oracle doc: Use ALTER ROLE to change the type of the role being granted (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY password), or use ALTER ROLE or ALTER USER to change the type of the user or role that is the grantee. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28023 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must revoke grants of this role to other user(s) first |
| Long Text: | The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and/or roles. Global roles cannot be granted to any user or role. |
| Repair Text: | From Oracle doc: Use REVOKE to revoke the role from other users or roles first. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28024 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | must revoke grants of external roles to this role/user |
| Long Text: | The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted; these must be revoked, since external roles cannot be granted to global users or roles. |
| Repair Text: | From Oracle doc: Use REVOKE to revoke the external roles from the user or role to be ALTERed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28025 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or null external name |
| Long Text: | The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name. |
| Repair Text: | From Oracle doc: Provide a valid external name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28026 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user with same external name already exists |
| Long Text: | The external name specified for the user being created or altered already exists for another user. |
| Repair Text: | From Oracle doc: External names must be unique among users. Specify another. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28027 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | privileged database links may be used by global users |
| Long Text: | Only users IDENTIFIED GLOBALLY may use a privileged database link. |
| Repair Text: | From Oracle doc: Either change the user to a global user or try to use a different database link. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28028 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not authenticate remote server |
| Long Text: | During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow. |
| Repair Text: | From Oracle doc: Consult the network security service documentation on how to properly configure the remote server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28029 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not authorize remote server for user %s |
| Long Text: | During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package. |
| Repair Text: | From Oracle doc: Grant the remote server the proper authorization to connect as the given global user, and check that the local server is not restricting access. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28030 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Server encountered problems accessing LDAP directory service |
| Long Text: | Unable to access LDAP directory service. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28035 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot Get Session Key for Authentication |
| Long Text: | Client and server cannot negotiate shared secret during logon. |
| Repair Text: | From Oracle doc: Contact your system administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy function schema %s is invalid |
| Long Text: | The schema was dropped after the policy associated with the function had been added to the object. |
| Repair Text: | From Oracle doc: Drop the policy and re-create it with a policy function owned by a valid user. Or re-create the user and the policy function under the new user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy already exists |
| Long Text: | A policy with the same name for the same object already exists. |
| Repair Text: | From Oracle doc: Check if the policy has already been added or use a different policy name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy does not exist |
| Long Text: | Try to drop/enable/refresh a non-existent policy. |
| Repair Text: | From Oracle doc: Correct the policy name argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | adding a policy to an object owned by SYS is not allowed |
| Long Text: | Try to add a policy to a table or a view owned by SYS. |
| Repair Text: | From Oracle doc: You cannot perform this operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28104 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy function or package is invalid |
| Long Text: | The function or package implementing a policy does not exist or was created with errors. |
| Repair Text: | From Oracle doc: Correct the function or package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | input value for argument #%s is not valid |
| Long Text: | Input values for the argument is missing or invalid. |
| Repair Text: | From Oracle doc: Correct the input values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy was disabled |
| Long Text: | Try to flush a disabled policy. |
| Repair Text: | From Oracle doc: If the policy is supposed to be enforced, it must be enabled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | circular row level security policies detected |
| Long Text: | Policies for the same object reference each other. |
| Repair Text: | From Oracle doc: Drop the policies. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the number of related policies has exceeded the limit of 16 |
| Long Text: | Too many policies are involved in the same objects. |
| Repair Text: | From Oracle doc: Drop one or more policies. Or combine a few of them into one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy function or package %s.%s has error |
| Long Text: | The policy function may have been dropped, or is no longer valid. |
| Repair Text: | From Oracle doc: Check the status of the function and correct the problem. Or re-create the policy with a valid function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privilege to evaluate policy predicate |
| Long Text: | Predicate has a subquery which contains objects that the owner of policy function does not have privilege to access. |
| Repair Text: | From Oracle doc: Grant appropriate privileges to the policy function owner. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to execute policy function |
| Long Text: | The policy function has one or more error during execution. |
| Repair Text: | From Oracle doc: Check the trace file and correct the errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy predicate has error |
| Long Text: | Policy function generates invalid predicate. |
| Repair Text: | From Oracle doc: Review the trace file for detailed error information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | policy with check option violation |
| Long Text: | Policy predicate was evaluated to FALSE with the updated values. |
| Repair Text: | From Oracle doc: Check the trace file and correct the errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to do direct path access |
| Long Text: | Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies. |
| Repair Text: | From Oracle doc: Ask the database administrator to do the operation. Note that users can work with security administrator to temporarily drop/disable the policies at time of export, import, or load, but this has security implication, and thus access of the database must be controlled carefully. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | proxy not authorized to connect as client |
| Long Text: | A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client. |
| Repair Text: | From Oracle doc: Grant the proxy user permission to perform actions on behalf of the client by using the ALTER USER... GRANT CONNECT command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | more than one user name specified for command |
| Long Text: | More than one user name was specified for an ALTER USER command. |
| Repair Text: | From Oracle doc: Try the command again with only one user name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | proxy user '%s' may not specify initial role '%s' on behalf of client '%s' |
| Long Text: | A proxy user attempted to specify an initial role for a client, but the client does not possess the role. |
| Repair Text: | From Oracle doc: Change the proxy user so that it does not specify the role or grant the role to the client. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid client initial role specified: '%s' |
| Long Text: | A role specified by a proxy user as an initial role to be activated upon connecting on behalf of a client is invalid. |
| Repair Text: | From Oracle doc: Connect again as the client specifying a valid role. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28154 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Proxy user may not act as client '%s' |
| Long Text: | A proxy user cannot assume the identity of a privileged user in order to limit the privileges that a proxy can possess. |
| Repair Text: | From Oracle doc: Execute the statement again, specifying a client other than a privileged user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user '%s' specified as a proxy is actually a role |
| Long Text: | A user specified in an AUDIT operation BY proxy ON BEHALF OF client is actually a role. |
| Repair Text: | From Oracle doc: Execute the statement again with a valid proxy user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28156 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Proxy user '%s' not authorized to set role '%s' for client '%s' |
| Long Text: | A proxy user has not been granted the right to use a role on behalf of a client. |
| Repair Text: | From Oracle doc: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28157 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Proxy user '%s' forbidden to set role '%s' for client '%s' |
| Long Text: | A proxy user was forbidden to use a role on behalf of a client through the command ALTER USER client GRANT CONNECT THROUGH proxy WITH ALL ROLES EXCEPT role. |
| Repair Text: | From Oracle doc: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28158 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing ALL keyword |
| Long Text: | Keyword missing. |
| Repair Text: | From Oracle doc: Provide missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28159 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing BEHALF keyword |
| Long Text: | Keyword missing. |
| Repair Text: | From Oracle doc: Provide missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing EXCEPT keyword |
| Long Text: | Keyword missing. |
| Repair Text: | From Oracle doc: Provide missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing ROLES keyword |
| Long Text: | Keyword missing. |
| Repair Text: | From Oracle doc: Provide missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing THROUGH keyword |
| Long Text: | Keyword missing. |
| Repair Text: | From Oracle doc: Provide missing keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GRANT already specified |
| Long Text: | The GRANT clause was specified twice. |
| Repair Text: | From Oracle doc: Use only one GRANT clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28164 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REVOKE already specified |
| Long Text: | The REVOKE clause was specified twice. |
| Repair Text: | From Oracle doc: Use only one REVOKE clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28165 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | proxy '%s' may not specify password-protected role '%s' for client '%s' |
| Long Text: | A proxy user attempted to activate a role on behalf of a client which has a password associated with it. Since the proxy does not have a password, this activation cannot be allowed. |
| Repair Text: | From Oracle doc: Attempt to activate a different role or change the role administratively so that there is no password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28166 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate rolename in list |
| Long Text: | The name of a role was specified more than once in a list. |
| Repair Text: | From Oracle doc: Repeat the command specifying the role once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28168 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempted to grant password-protected role |
| Long Text: | An ALTER USER ... GRANT CONNECT command was attempted specifying a role that is protected by a password as a role which the proxy may execute on behalf of a client. |
| Repair Text: | From Oracle doc: Either specify a role that does not have a password or alter the role so that a password is not required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28231 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid input to Obfuscation toolkit |
| Long Text: | An empty input was given to the obfuscation toolkit. |
| Repair Text: | From Oracle doc: Make sure that the input corresponding to the PL/SQL function is not empty. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28232 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid input size for Obfuscation toolkit |
| Long Text: | Input to DES encryption/decryption routine not a multiple of 8 bytes. |
| Repair Text: | From Oracle doc: Make sure that the input corresponding to the PL/SQL function is a multiple of 8 bytes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | connection from ORACLE to a non-Oracle system returned this message: |
| Long Text: | The cause is explained in the forwarded message. |
| Repair Text: | From Oracle doc: See the non-Oracle system's documentation of the forwarded message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | communication error on heterogeneous database link |
| Long Text: | An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system. |
| Repair Text: | From Oracle doc: See the documentation for the non-Oracle system for an explanation of the second error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal communication error on heterogeneous database link |
| Long Text: | A communication error internal to Oracle's heterogeneous services has occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bind value cannot be translated into SQL text for non-Oracle system |
| Long Text: | A SQL statement used bind variables on a Heterogeneous Services database link to a non-Oracle system, but the non-Oracle system does not support bind variables. |
| Repair Text: | From Oracle doc: Change your SQL statement so that it does not use bind variables. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ROWID not found in ROWID cache for heterogeneous database link |
| Long Text: | The ROWID cache for Heterogeneous Services held no entry that corresponds to the specified ROWID. The ROWID entry may have been overwritten in the ROWID cache. |
| Repair Text: | From Oracle doc: Enlarge the Heterogeneous Services ROWID cache size by increasing the value of the initialization parameter ROWID_CACHE_SIZE in the server data dictionary by using the DBMS_HS PL/SQL package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot get non-Oracle system capabilities from %s |
| Long Text: | Oracle was unable to retrieve capability information for the non-Oracle system connected through a heterogeneous database link. This capability information should be stored in data dictionary tables viewable with the HS_CLASS_CAPS or HS_INST_CAPS data dictionary views. |
| Repair Text: | From Oracle doc: Contact the database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parse error in data dictionary translation for %s stored in %s |
| Long Text: | A reference to an Oracle data dictionary table or view name on a heterogeneous database link to a non-Oracle system could not be translated. The Oracle data dictionary tables shown with view HS_CLASS_DD contain invalid SQL for the data dictionary translation. |
| Repair Text: | From Oracle doc: Contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in data dictionary view %s |
| Long Text: | The initialization parameter table for the Heterogeneous Services was not available, or its structure (number of columns or column types) was incorrect. |
| Repair Text: | From Oracle doc: Verify correct installation of the following Heterogeneous Services' initialization parameter views: HS_CLASS_INIT and HS_INST_INIT. If these views are not available, make sure you ran the script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid value %s for Heterogeneous Services initialization parameter %s |
| Long Text: | The specified Heterogeneous Services initialization parameter had an invalid value when attempting to connect to a non-Oracle system. |
| Repair Text: | From Oracle doc: Check the Heterogeneous Services documentation to determine acceptable values, and update that parameter in HS_INST_INIT using a PL/SQL procedure in the DBMS_HS package. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to establish a connection to non-Oracle system |
| Long Text: | Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system. |
| Repair Text: | From Oracle doc: Check the Net8 service name definition in the following places: the USING clause of the CREATE DATABASE LINK statement the TNSNAMES.ORA file the Oracle Names Server The following are possible reasons for name mismatches: The USING clause in the CREATE DATABASE LINK statement has to match the service name defined in the TNSNAMES.ORA file or in the Oracle Names Server. The protocol-specific information in the service name definition must match the protocol-specific definition of the responding listener. The SID=name in the service name definition (in the TNSNAMES.ORA file or in Oracle Names Server) must match the value in the LISTENER.ORA file for the responding listener. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | heterogeneous database link initialization failed |
| Long Text: | Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system. |
| Repair Text: | From Oracle doc: Make sure the non-Oracle system is up and running and that all of the environment and initialization values for the agent are set correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28511 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | lost RPC connection to heterogeneous remote agent using SID=%s |
| Long Text: | A fatal error occurred in one of the following places: the connection between the Oracle server and the agent the heterogeneous services remote agent itself the connection to the non-Oracle system This error occurred after communication had been established successfully. |
| Repair Text: | From Oracle doc: Check for network problems and remote host crashes. The problem is probably in the agent software. If so, contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot get data dictionary translations from %s |
| Long Text: | Oracle was unable to retrieve data dictionary translation information for the non-Oracle system connected through a heterogeneous database link. This data dictionary translation information should be stored in data dictionary tables viewable with the HS_CLASS_DD or HS_INST_DD data dictionary views. |
| Repair Text: | From Oracle doc: Ask your database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error in heterogeneous remote agent |
| Long Text: | An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link. |
| Repair Text: | From Oracle doc: Make a note of how the error was produced and contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | heterogeneous database link initialization could not convert system date |
| Long Text: | The system date was not retrievable. |
| Repair Text: | From Oracle doc: Verify that the Oracle server's host machine and operating system are operational. This error should not occur unless low level system functions are failing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28515 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot get external object definitions from %s |
| Long Text: | Oracle was unable to retrieve definitions of distributed external procedures or remote libraries registered for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is malformed. |
| Repair Text: | From Oracle doc: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28518 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data dictionary translation has illegal translation type |
| Long Text: | A data dictionary translation definition, either in the Oracle server data dictionary or in data dictionary content uploaded from a Heterogeneous Services agent, specified an illegal translation type code. Legal values are 'T' or 't' for 'translate', 'M' or 'm' for 'mimic'. Information on the exact data dictionary translation causing the error is written to a trace (*.TRC) file for the Oracle instance and to the Oracle instance's alert log. This error occurs when a Heterogeneous Services agent uploads data dictionary content to an Oracle server on the first connection from the server to the agent. |
| Repair Text: | From Oracle doc: Contact the customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28519 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no heterogeneous data dictionary translations available |
| Long Text: | The Oracle server's data dictionary did not define data dictionary translations for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled. |
| Repair Text: | From Oracle doc: Ask a database administrator to resolve this problem. The easiest solution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28520 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error initializing heterogeneous data dictionary translations |
| Long Text: | Oracle was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly. |
| Repair Text: | From Oracle doc: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28521 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no heterogeneous capability information available |
| Long Text: | The Oracle server's data dictionary did not contain capability definitions for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled. |
| Repair Text: | From Oracle doc: Ask a database administrator to resolve this problem. The easiest resolution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28522 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error initializing heterogeneous capabilities |
| Long Text: | Oracle was unable to retrieve capability definitions for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly. |
| Repair Text: | From Oracle doc: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28523 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE and heterogeneous agent are incompatible versions |
| Long Text: | An operation on a database link attempted to connect to a non-Oracle system, but the Oracle instance and the agent process for the non-Oracle system are incompatible. |
| Repair Text: | From Oracle doc: Ask your database administrator to confirm configuration of both the Oracle instance and the agent. Additional information on the version incompatibility is logged in trace (*.TRC) files, the Oracle instance and the agent, and in the Oracle instance's alert log. Check the documentation for your agent to find out which releases of the Oracle Server are supported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28525 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to create Heterogeneous Services error message text |
| Long Text: | Incorrect arguments were passed into the error message creation routine. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28526 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid describe information returned to Heterogeneous Services |
| Long Text: | The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services' non-Oracle system agent. |
| Repair Text: | From Oracle doc: Contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28527 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Heterogeneous Services datatype mapping error |
| Long Text: | Either an Oracle datatype could not be mapped to a non-Oracle datatype, or a non-Oracle datatype could not be mapped to an Oracle datatype. These mappings are defined as capability definitions in the Oracle server's data dictionary. |
| Repair Text: | From Oracle doc: Verify that the Oracle server's data dictionary has been initialized with correct capability definitions for the connected FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect, a database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. If the error persists contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28528 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Heterogeneous Services datatype conversion error |
| Long Text: | Either an Oracle datatype could not be converted to a non-Oracle datatype, or a non-Oracle datatype could not be converted to an Oracle datatype. The following are possible reasons for the conversion failure: overflow problems (in the case of numbers) length limitations (in the case of character strings) invalid values passed into the conversion routines |
| Repair Text: | From Oracle doc: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it may not be possible to convert the value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28529 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or missing parameter in Net8 service name definition |
| Long Text: | There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names Server. |
| Repair Text: | From Oracle doc: Ask your database administrator to make sure the information in the Net8 service definition is correct and complete. The correct information that should be included in the Net8 service definition can be found in the agent's documentation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28530 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Heterogeneous Services initialization error in NLS language ID |
| Long Text: | Heterogeneous Services was unable to initialize an NLS language ID. Both the Oracle server and the Heterogeneous Services agent for the connected non-Oracle system must have language IDs. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28533 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Heterogeneous Services coercion handling error |
| Long Text: | The Heterogeneous Services encountered an error in coercion handling. The HS can, if the agent vendor so chooses, perform extra processing on SQL statements that contain implicit coercions or that contain coercion functions such as TO_CHAR, TO_NUMBER or TO_DATE. This functionality is controlled by coercion-related capabilities. HS logic reports this error when it encounters an error in one of these capability definitions. |
| Repair Text: | From Oracle doc: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Heterogeneous Services preprocessing error |
| Long Text: | One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the HS could encounter errors when it attempts to do the preprocessing. If it does then this error will be signaled. |
| Repair Text: | From Oracle doc: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28535 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid Heterogeneous Services context |
| Long Text: | A Heterogeneous Services agent's driver module called an HS service routine with an invalid HS context value. This probably is a logic error in the driver. |
| Repair Text: | From Oracle doc: Contact customer support of the agent vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28536 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in processing Heterogeneous Services initialization parameters |
| Long Text: | An error described by a subsequent error message prevented successful processing of Heterogeneous Services initialization parameters from the Oracle server data dictionary. |
| Repair Text: | From Oracle doc: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and HS_ALL_INITS. Look for conditions which could produce the error identified in the error message immediately following this one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28550 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pass-through SQL: cursor not found |
| Long Text: | A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor. |
| Repair Text: | From Oracle doc: Use a cursor number returned by the pass-through SQL OPEN_CURSOR call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pass-through SQL: SQL parse error |
| Long Text: | A non-Oracle system rejected text supplied as a pass-through SQL statement. |
| Repair Text: | From Oracle doc: Ensure that the SQL supplied to the pass-through SQL PARSE call is legal for the non-Oracle system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pass-through SQL: call flow error |
| Long Text: | A pass-through SQL function was called in an invalid order. |
| Repair Text: | From Oracle doc: Correct program flow by changing the order of API calls to match the flow described in the manual. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28553 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pass-through SQL: invalid bind-variable position |
| Long Text: | A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text. |
| Repair Text: | From Oracle doc: Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28554 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pass-through SQL: out of cursors |
| Long Text: | The maximum number of open cursors has been exceeded. |
| Repair Text: | From Oracle doc: Close open cursors by using the pass-through SQL CLOSE_CURSOR function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28555 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pass-through SQL: required parameter missing or NULL |
| Long Text: | An attempt was made to pass a NULL value to a non-NULL parameter. |
| Repair Text: | From Oracle doc: Use a non-NULL value for the parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28556 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | authorization insufficient to access table |
| Long Text: | A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns. |
| Repair Text: | From Oracle doc: Contact the database administrator for the non-Oracle system. The database administrator can grant permission to access the privileged table or columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28557 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown %s for database link to non-Oracle system |
| Long Text: | When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. Oracle requires these names to configure the heterogeneous database link. |
| Repair Text: | From Oracle doc: Contact the database administrator to check setup of the connection and the Heterogeneous Services agent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28558 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | HS_FDS_CONNECT_STRING undefined for non-Oracle system |
| Long Text: | A database link to a non-Oracle system had no HS_FDS_CONNECT_STRING initialization parameter in the Oracle server's data dictionary for Heterogeneous Services. Without this parameter, the connection could not be completed. |
| Repair Text: | From Oracle doc: Contact your database administrator to verify correct setup of an HS_FDS_CONNECT_STRING entry in the Oracle Heterogeneous Services data dictionary (see HS_INST_INITS view in the Oracle8 Reference book). It may be necessary to use PL/SQL procedures in the SYS.DBMS_HS package to create or replace an entry for the connection's FDS_CLASS_NAME and FDS_INST_NAME. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28559 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | FDS_CLASS_NAME is %s, FDS_INST_NAME is %s |
| Long Text: | An associated error was reported in another message, and this message supplies supplementary information to assist diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the Oracle data dictionary that direct operation of Heterogeneous Services on a database link to a non-Oracle data store. |
| Repair Text: | From Oracle doc: Use the FDS_CLASS_NAME and FDS_INST_NAME values to check Oracle data dictionary contents when necessary to diagnose the cause of the associated error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28560 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in configuration of agent process |
| Long Text: | An Oracle server invoked a function not supported by the connected agent (Heterogeneous Services or external procedures). The most probable cause is incorrect Net8 setup, resulting in use of the wrong agent executable. |
| Repair Text: | From Oracle doc: Check Net8 administration in the following ways: When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the Oracle server uses the correct SID. Check LISTENER.ORA on the agent's host machine to assure that this SID refers to the correct agent executable in its (PROGRAM=...) clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28561 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to set date format on non-Oracle system |
| Long Text: | Initialization of a Heterogeneous Services connection to set the date format to be used on the connected non-Oracle system. |
| Repair Text: | From Oracle doc: If the Oracle data dictionary supplies a value for the HS_NLS_DATE_FORMAT parameter, confirm that this value is formatted correctly by the rules of the non-Oracle system. Also check for additional information in log and trace files generated by the Heterogeneous Services agent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28575 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to open RPC connection to external procedure agent |
| Long Text: | Initialization of a network connection to the external procedure agent did not succeed. This problem can be caused by network problems, incorrect listener configuration, or incorrect transfer code. |
| Repair Text: | From Oracle doc: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or check Oracle Names Server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28576 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | lost RPC connection to external procedure agent |
| Long Text: | A fatal error occurred in either an RPC network connection, the external procedure agent, or the invoked 3GL after communication had been established successfully. |
| Repair Text: | From Oracle doc: First check the 3GL code you are invoking; the most likely cause of this error is abnormal termination of the invoked "C" routine. If this is not the case, check for network problems. Correct the problem if you find it. If all components appear to be normal but the problem persists, the problem could be an internal logic error in the RPC transfer code. Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28577 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument %s of external procedure %s has unsupported datatype %s |
| Long Text: | While transferring external procedure arguments to the agent, an unsupported datatype was detected. |
| Repair Text: | From Oracle doc: Check your documentation for the supported datatypes of external procedure arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28578 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | protocol error during callback from an external procedure |
| Long Text: | An internal protocol error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28579 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | network error during callback from external procedure agent |
| Long Text: | An internal network error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28580 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recursive external procedures are not supported |
| Long Text: | A callback from within a user's 3GL routine resulted in the invocation of another external procedure. |
| Repair Text: | From Oracle doc: Make sure that the SQL code executed in a callback does not directly call another external procedure, or indirectly results in another external procedure, such as triggers calling external procedures, PL/SQL procedures calling external procedures, and so on. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28581 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | protocol error while executing recursive external procedure |
| Long Text: | An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28582 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a direct connection to this agent is not allowed |
| Long Text: | A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed. |
| Repair Text: | From Oracle doc: When executing the CONNECT statement, make sure your database link or network alias is not pointing to a Heterogeneous Option agent or an external procedure agent. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28590 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | agent control utility: illegal or badly formed command |
| Long Text: | The user has issued an unrecognized or syntactically incorrect command. |
| Repair Text: | From Oracle doc: Refer to documentation and correct the syntax of the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28591 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | agent control utility: unable to access parameter file |
| Long Text: | The agent control utility was unable to access its parameter file. This could be because it could not find its ADMIN directory or because permissions on directory were not correctly set. |
| Repair Text: | From Oracle doc: The agent control utility puts its parameter file in either the directory pointed to by the environment variable AGTCTL_ADMIN or in the directory pointed to by the environment variable TNS_ADMIN. Make sure that at least one of these environment variables is set and that it points to a directory that the agent has access to. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28592 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | agent control utility: agent SID not set |
| Long Text: | The agent needs to know the value of the AGENT_SID parameter before it can process any commands. If it does not have a value for AGENT_SID then all commands will fail. |
| Repair Text: | From Oracle doc: Issue the command SET AGENT_SID value and then retry the command that failed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28593 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | agent control utility: command terminated with error |
| Long Text: | An error occurred during the processing of the command. There could be several causes. A SET or an UNSET command could have been issued after the agent was started. This is illegal. The user may have attempted to start two agents with the same SID value or the user could have attempted to shut down an agent that is no longer running. |
| Repair Text: | From Oracle doc: If the user wishes to issue a SET or an UNSET command, he should make sure the agent is shut down first by issuing the SHUTDOWN command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28594 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | agent control utility: invalid parameter name |
| Long Text: | The user tried to set or unset an invalid agent parameter. |
| Repair Text: | From Oracle doc: Refer to documentation and correct the parameter name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28601 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid [no]MINIMIZE option |
| Long Text: | User did not type this alter table table_name MINIMIZE RECORDS_PER_BLOCK or alter table table_name NOMINIMIZE RECORDS_PER_BLOCK. |
| Repair Text: | From Oracle doc: Re-enter correct SQL command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28602 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | statement not permitted on tables containing bitmap indexes |
| Long Text: | Table has bitmap indexes and user is minimizing or nominalizing RECORDS_PER_BLOCK. |
| Repair Text: | From Oracle doc: Drop all bitmap indexes before changing RECORDS_PER_BLOCK. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28603 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | statement not permitted on empty tables |
| Long Text: | Table is empty and statement does not work on empty tables. |
| Repair Text: | From Oracle doc: Try statement after loading your data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28605 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | bitmap indexes cannot be reversed |
| Long Text: | An attempt was made to create reverse bitmap index. This is not supported. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28611 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | bitmap index is corrupted - see trace file for diagnostics |
| Long Text: | Validate Index detected bitmap corruption in its argument index. |
| Repair Text: | From Oracle doc: Drop this bitmap index and create a new one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28650 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Primary index on an IOT cannot be rebuilt |
| Long Text: | An attempt was made to issue alter index rebuild on IOT-TOP. |
| Repair Text: | From Oracle doc: Use Alter table MOVE to reorganize the table(IOT). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28651 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Primary index on IOTs can not be marked unusable |
| Long Text: | An attempt was made to mark IOT-TOP unusable through ALTER INDEX. |
| Repair Text: | From Oracle doc: Remove the option UNUSABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28652 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | overflow segment attributes cannot be specified |
| Long Text: | During ALTER MOVE ONLINE of a index-organized table, the user attempted to enter one or more of the following options: OVERFLOW, PCTTHRESHOLD,INCLUDING. |
| Repair Text: | From Oracle doc: Remove the illegal option(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28653 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tables must both be index-organized |
| Long Text: | An attempt was made to exchange a non-IOT table/partition with a partition/table respectively. |
| Repair Text: | From Oracle doc: Ensure that non-partitioned and partitioned tables are both index-organized. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28654 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table and partition not overflow compatible |
| Long Text: | If one of the tables (partitioned/non-partitioned) has overflow data segment and the other one does not. |
| Repair Text: | From Oracle doc: Ensure that non-partitioned and partitioned tables both have overflow data segment or neither one does. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28655 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | Alter table add overflow syntax error |
| Long Text: | Syntax error. |
| Repair Text: | From Oracle doc: Check the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28656 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incomplete attribute specification |
| Long Text: | The attribute specification is not done for all partitions. |
| Repair Text: | From Oracle doc: Specify the storage attributes either for ALL partitions or NONE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28658 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | This operation is supported only for Index-Organized tables |
| Long Text: | Attempt to perform some IOT specific operation on a non-IOT. This is not supported. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28659 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | COMPRESS must be specified at object level first |
| Long Text: | An attempt was made to specify COMPRESS at the partition level without first specifying it at the table level. |
| Repair Text: | From Oracle doc: Specify COMPRESS at the table level. Use ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES COMPRESS ... |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28660 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Partitioned Index-Organized table may not be MOVEd as a whole |
| Long Text: | An attempt was made to MOVE a partitioned index-organized table as a whole. This is not supported. |
| Repair Text: | From Oracle doc: Do not try to MOVE a partitioned index-organized table as a whole. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28661 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Object already has COMPRESS clause specified |
| Long Text: | An attempt was made to specify COMPRESS for an index-organized table/index which already has a compression clause. This attribute can only be specified at creation time. |
| Repair Text: | From Oracle doc: Do not specify COMPRESS for an index-organized table/index which already has a compression clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28662 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | IOT index and overflow segments must share the same LOGGING attribute |
| Long Text: | An attempt was made to specify LOGGING for one segment and NOLOGGING for the other segment. |
| Repair Text: | From Oracle doc: Use the same attribute value for both segments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-28663 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW |
| Long Text: | An attempt was made to specify LOGGING for an ALTER TABLE ADD OVERFLOW statement. |
| Repair Text: | From Oracle doc: Do not specify LOGGING in this context. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29250 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid index specifed in call to dbms_sql.bind_array |
| Long Text: | An invalid index was specified in a call to BIND_ARRAY of DBMS_SQL. The index may have been null or of an improper value. |
| Repair Text: | From Oracle doc: Correct the index value by modifying your PL/SQL program and try the BIND_ARRAY call again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29251 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Index1 is greater than Index2 in call to dbms_sql.bind_array |
| Long Text: | The value of index1 was greater than the value for index2 in the call to BIND_ARRAY. This is illegal since the elements of the table that will be bound are those with indexes greater than or equal to index1 and less than or equal to index2. |
| Repair Text: | From Oracle doc: Correct the value of the two indexes and try the call to again BIND_ARRAY. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29252 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | collection does not contain elements at index locations in call to dbms_sql.bind_array |
| Long Text: | The bound table does not contain elements at both index locations in call to BIND_ARRAY of DBMS_SQL. This is illegal. Both index locations must contain elements. In other words tab.exists(index1) and tab.exists(index2) must both return true. |
| Repair Text: | From Oracle doc: Either modify the two indexes or the contents of the table and try the call again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29253 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid count argument passed to procedure dbms_sql.define_array |
| Long Text: | The count argument specified in the call to procedure DEFINE_ARRAY of package DBMS_SQL had an invalid value. Invalid values are negative numbers and nulls. The argument must be a positive integer. |
| Repair Text: | From Oracle doc: Correct your PL/SQL program so that only valid arguments are passed to DEFINE_ARRAY and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29254 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid lower_bound argument passed to procedure dbms_sql.define_array |
| Long Text: | The LOWER_BOUND argument specified in the call to procedure DEFINE_ARRAY had an invalid value. Legal values are all integers (both positive and negative) including zero. The null value is illegal. |
| Repair Text: | From Oracle doc: Correct your PL/SQL program so that only valid arguments are passed to DEFINE_ARRAY and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29255 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cursor contains both bind and define arrays which is not permissible |
| Long Text: | Both DEFINE_ARRAY and BIND_ARRAY have been called on this cursor. This is illegal. It is not possible for a cursor to both contain array binds and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and array binds to bind PL/SQL tables to non-select queries. |
| Repair Text: | From Oracle doc: Modify your PL/SQL program to only perform calls to one of the two functions depending on the kind of cursor at hand. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29256 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cursor contains both regular and array defines which is illegal |
| Long Text: | Both DEFINE_ARRAY and DEFINE_COLUMN have been called on this cursor. This is illegal. It is not possible for a cursor to both contain regular and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and regular defines to move data from select queries into PL/SQL variables. |
| Repair Text: | From Oracle doc: Modify your PL/SQL program to only perform calls to one of the two functions depending on the situation at hand. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29300 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ORACLE error, tablespace point-in-time recovery |
| Long Text: | Another Oracle error occurred in the DBMS_PITR package. |
| Repair Text: | From Oracle doc: See the text of the error message for a description of the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29301 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong DBMS_PITR package function/procedure order |
| Long Text: | The DBMS_PITR package function/procedure was called in an incorrect order. |
| Repair Text: | From Oracle doc: Restart tablespace point-in-time recovery with a correct procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29302 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database is not open clone |
| Long Text: | The database was not opened as a clone database. |
| Repair Text: | From Oracle doc: Mount the database clone and open the database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29303 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user does not login as SYS |
| Long Text: | The user did not log in as SYS to perform tablespace point-in-time recovery in a clone database. |
| Repair Text: | From Oracle doc: Log in as SYS and restart tablespace point-in-time recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29304 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' does not exist |
| Long Text: | The selected tablespace does not exist in the database. |
| Repair Text: | From Oracle doc: Check the list of tablespaces in V$TABLESPACE and select a valid tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29305 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot point-in-time recover tablespace '%s' |
| Long Text: | An attempt was made to ALTER the tablespace to be read only. |
| Repair Text: | From Oracle doc: Check if the tablespace is SYSTEM or with online rollback segment. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29306 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s is not online |
| Long Text: | The selected datafile was not online. |
| Repair Text: | From Oracle doc: Bring the datafile online and rename it if necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29307 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s error, %s |
| Long Text: | The datafile is not ready for tablespace point-in-time recovery. |
| Repair Text: | From Oracle doc: Check the correct tablespace point-in-time recovery procedure. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29308 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | view TS_PITR_CHECK failure |
| Long Text: | Some objects which crossed the boundary of the recovery set were not allowed in the tablespace point-in-time recovery. |
| Repair Text: | From Oracle doc: Query TS_PITR_CHECK and resolve the boundary crossing objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29309 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | export dump file was generated by different version of DBMS_PITR package |
| Long Text: | The version of DBMS_PITR is different from the version of the cloned database. |
| Repair Text: | From Oracle doc: Load the version of DBMS_PITR which matches the version of the cloned database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29310 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database is not open, or opened as a clone |
| Long Text: | Either the database was not open, or an attempt was made to open it as a cloned database. |
| Repair Text: | From Oracle doc: Open the production database instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29311 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | export dump file was not generated by this database, %s does not match |
| Long Text: | The export dump files were imported to an incorrect database. |
| Repair Text: | From Oracle doc: Open the correct production database and try the import again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29312 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database not compatible, %s %s |
| Long Text: | A point-in-time tablespace was chosen to perform the recovery, but the current database is not compatible with the database that was used to create the point-in-time tablespace. |
| Repair Text: | From Oracle doc: Choose a point-in-time and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29313 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' cannot be imported twice |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact your database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29314 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is not OFFLINE FOR RECOVER nor READ ONLY |
| Long Text: | Tablespace clean SCN is either 0 or invalid. |
| Repair Text: | From Oracle doc: ALTER the tablespace OFFLINE FOR RECOVER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29315 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' has been recreated |
| Long Text: | An attempt was made to recover a tablespace to a point-in-time before it was re-created. |
| Repair Text: | From Oracle doc: Choose a different point in time for recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29316 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s been imported twice |
| Long Text: | This is an internal error. |
| Repair Text: | From Oracle doc: Contact your database administrator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29317 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s does not exist |
| Long Text: | The specified datafile could not be found in the production database. |
| Repair Text: | From Oracle doc: Copy the datafile from the clone database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29318 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s is online |
| Long Text: | The datafile is online. |
| Repair Text: | From Oracle doc: Take the datafile offline. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29319 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s is not correct |
| Long Text: | An incorrect datafile was copied to the production database. The datafile information in the export dump file differs with the information in the datafile in the production database. |
| Repair Text: | From Oracle doc: Copy the datafile from the clone database to the production database. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29320 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile header error |
| Long Text: | An error occurred during reading datafile header. |
| Repair Text: | From Oracle doc: Copy the correct datafile from the clone database to the production database, then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29321 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many datafiles added since the point-in-time |
| Long Text: | Too many datafiles were added to the recovery set since the point-in-time recovery. It is assumed that no more than 100 datafiles were added since the point-in-time. |
| Repair Text: | From Oracle doc: Divide the recovery set into smaller subsets and retry. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29322 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SCN %s size too long -- maximum size 58 bytes/characters |
| Long Text: | Too many characters in specifying the SCN string |
| Repair Text: | From Oracle doc: Remove all unnecessary characters. Only 15 characters are required for both the hex and decimal representation of the 48 bit SCN. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29323 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SET COMPATIBILITY command cannot be used for releases before 8.0.0 |
| Long Text: | The rolling release feature was first implemented in 8.0.3. |
| Repair Text: | From Oracle doc: Try 8.0.3 or later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29324 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SET COMPATIBILITY release %s format is wrong |
| Long Text: | It should be of the form 8.x.x. |
| Repair Text: | From Oracle doc: Use the correct format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29325 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SET COMPATIBILITY release number mismatches compatibility release number |
| Long Text: | In 8.0.3, it should be the same as compatibility release number. |
| Repair Text: | From Oracle doc: Specify the same as the COMPATIBLE initialization parameter. Note that this cannot be a release number less than 8.0.0. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29326 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified SET COMPATIBILITY release number reduced to %s.%s.%s.%s.%s |
| Long Text: | One or more instances had a lower release number. |
| Repair Text: | From Oracle doc: To roll the release to the specified number, all instances will need to migrate to the same release number or higher. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29327 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported client compatibility mode used when talking to the server |
| Long Text: | The client compatibility mode is higher than the version of the server. |
| Repair Text: | From Oracle doc: Using SET COMPATIBILITY command, specify the same release number as the server. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' is not read only |
| Long Text: | The tablespace is not read only. |
| Repair Text: | From Oracle doc: Make the tablespace read only and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29336 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Internal error [%s] [%s] from DBMS_PLUGTS |
| Long Text: | Internal error from package DBMS_PLUGTS. |
| Repair Text: | From Oracle doc: Call Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29337 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Failed to validate the file header of datafile %s |
| Long Text: | The system failed to validate the file header of the referred datafile. The datafile maybe missing. The content in the datafile header may be inconsistent with that in the control file. |
| Repair Text: | From Oracle doc: Make sure the referred datafile exists. Make sure it is in a valid state. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29338 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datafile %s is in an undesired state (%s, %s) |
| Long Text: | The referred datafile is not in a state ready for tablespace copy operation. For example, the datafile may be offline. The datafile needs to be ONLINE, and either READ ONLY or READ WRITE. |
| Repair Text: | From Oracle doc: Put the datafile into the desired state. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29339 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace block size %s does not match database block size %s |
| Long Text: | The block size of the tablespace to be plugged in does not match the block size of the database. Plugging a tablespace into a database with a different block size is not supported. |
| Repair Text: | From Oracle doc: Use a different way to move data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | export file appears to be corrupted: [%s] [%s] [%s] |
| Long Text: | This is caused either by a corrupted export file or by an Oracle internal error. |
| Repair Text: | From Oracle doc: Make sure the export file used for transportable tablespace is not corrupted. If the error still occurs, call Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The transportable set is not self-contained |
| Long Text: | The set of objects in the set of tablespaces selected are not self-contained. |
| Repair Text: | From Oracle doc: Consider using different export options, or removing some of the pointers that caused the violation, or selecting a different set of tablespaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user %s does not exist in the database |
| Long Text: | The referred user is one of the owners of data in the pluggable set. This user does not exist in the database. |
| Repair Text: | From Oracle doc: Consider either creating the user in the database or map the user to a different user via FROM_USER and TO_USER import options. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29343 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user %s (mapped from user %s) does not exist in the database |
| Long Text: | The referred user is one of the owners of data in the pluggable set. This user does not exist in the database. |
| Repair Text: | From Oracle doc: Consider either creating the user or map the original user to a different user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Owner validation failed - failed to match owner '%s' |
| Long Text: | The system failed to match the referenced owner. There are two cases in which this may occur: This user owns data in the transportable set, but this user is not specified in the TTS_OWNERS list of the import command line option, assuming that TTS_OWNERS is specified. This user is specified in the TTS_OWNER list, but this user does not own any data in the transportable set. |
| Repair Text: | From Oracle doc: Retry the import with a different OWNER list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not plug a tablespace into a database using a different character set |
| Long Text: | Oracle does not support plugging a tablespace into a database using a different character set. |
| Repair Text: | From Oracle doc: Use import/export or unload/load to move data instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29346 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid tablespace list |
| Long Text: | The tablespace list supplied to DBMS_TTS.TRANSPORT_SET_CHECK. PL/SQL routine is in an incorrect format. |
| Repair Text: | From Oracle doc: Check PL/SQL User's Guide and Reference and use the correct format. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29347 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Tablespace name validation failed - failed to match tablespace '%s' |
| Long Text: | The system failed to match the referenced tablespace. There are two case in which this may happen: This tablespace is in the transportable set, but it is not specified in the TABLESPACES list of the import command line option, assuming that TABLESPACES is specified. This tablespace is in the TABLESPACES list, but it is not in the transportable set. |
| Repair Text: | From Oracle doc: Retry the operation with the correct TABLESPACES list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29348 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | You must specify the datafiles to be plugged in |
| Long Text: | The datafiles to be plugged in are not specified. |
| Repair Text: | From Oracle doc: Specify the datafiles via the import DATAFILES command line option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29349 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | tablespace '%s' already exists |
| Long Text: | An attempt was made to plug-in a tablespace which already exists. |
| Repair Text: | From Oracle doc: Drop the offending tablespace if possible. Otherwise use a different method (for example, import/export) to move data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | server version %s incompatible with package %s version %s |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | can not transport system or temporary tablespace '%s' |
| Long Text: | The referenced tablespace is either the system tablespace or a temporary tablespace. |
| Repair Text: | From Oracle doc: Do not include this tablespace in the transportable set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29355 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL or invalid %s argument specified |
| Long Text: | The named argument was either invalid or specified as a NULL. |
| Repair Text: | From Oracle doc: Specify non-null, valid arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29356 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | MAX_ACTIVE_SESS_TARGET_P1 and PARALLEL_DEGREE_LIMIT_P1 can be specified only for directives that refer to consumer groups |
| Long Text: | The above parameters were specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER where the GROUP_OR_SUBPLAN argument is a resource plan. |
| Repair Text: | From Oracle doc: Specify these parameters only for consumer group directives. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29357 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s already exists |
| Long Text: | The name specified as argument to procedure CREATE_PLAN, CREATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER was already in use. |
| Repair Text: | From Oracle doc: Specify an unused name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29358 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resource plan %s does not exist |
| Long Text: | An invalid plan name was specified as an argument to procedure UPDATE_PLAN of package DBMS_RESOURCE_MANAGER. |
| Repair Text: | From Oracle doc: Specify an existing plan name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29359 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid method name %s specified for resource plan %s |
| Long Text: | An invalid method was specified as an argument to procedure CREATE_PLAN or UPDATE_PLAN of package DBMS_RESOURCE_MANAGER. |
| Repair Text: | From Oracle doc: Specify a valid method name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | retry operation. Too much concurrent activity |
| Long Text: | An attempt was made to revoke the switch consumer group privilege from a user for his/her initial consumer group but someone is modifying the user in another session. |
| Repair Text: | From Oracle doc: Retry the operation later. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | percentage %s is outside valid range of 0 to 100 |
| Long Text: | An invalid percentage value was specified. |
| Repair Text: | From Oracle doc: Specify a percentage value between 0 and 100 inclusive. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | plan directive %s, %s does not exist |
| Long Text: | A non-existent plan directive was specified for procedure UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER. |
| Repair Text: | From Oracle doc: Specify an existing plan directive for update. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | plan directive %s, %s is mandatory and cannot be modified or deleted |
| Long Text: | An attempt was made to modify a mandatory plan directive. |
| Repair Text: | From Oracle doc: Do not attempt to modify mandatory plan directives because they are required by the Resource Manager and cannot be modified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29364 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | plan directive %s, %s already exists |
| Long Text: | An attempt was made to create a plan directive that already exists. |
| Repair Text: | From Oracle doc: Retry the create operation using different values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29365 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL or invalid GROUP_OR_SUBPLAN argument specified |
| Long Text: | A NULL or invalid GROUP_OR_SUBPLAN was specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER. |
| Repair Text: | From Oracle doc: Specify a non-NULL, valid argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29366 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid CONSUMER_GROUP argument specified |
| Long Text: | An invalid consumer group name was specified. |
| Repair Text: | From Oracle doc: Specify a non-NULL, valid consumer group name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29367 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object %s does not exist |
| Long Text: | A non-existent object name was specified as an argument to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER. |
| Repair Text: | From Oracle doc: Specify a valid plan or consumer group name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29368 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | consumer group %s does not exist |
| Long Text: | An non-existent consumer group was specified. |
| Repair Text: | From Oracle doc: Specify an existing consumer group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid method name %s specified for consumer group %s |
| Long Text: | An invalid method name was specified as an argument to procedure CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER. |
| Repair Text: | From Oracle doc: Specify a valid method name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29370 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | pending area is already active |
| Long Text: | An attempt was made to activate a pending area that is already active. |
| Repair Text: | From Oracle doc: Wait until the pending area is no longer active; then, retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29371 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | pending area is not active |
| Long Text: | An attempt was made to make changes without creating a pending area. |
| Repair Text: | From Oracle doc: Invoke procedure CREATE_PENDING_AREA before making any changes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29372 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | identifier %s is too long; it must be less than %s characters |
| Long Text: | An attempt was made to specify an identifier that is more than 30 characters long. |
| Repair Text: | From Oracle doc: Use an identifier that is 30 characters or less in length. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29373 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resource manager is not on |
| Long Text: | An attempt was made to execute an operation that cannot be executed with the resource manager being off. |
| Repair Text: | From Oracle doc: Turn on the resource manager and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29374 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resource plan %s in top-plan %s has no plan directives |
| Long Text: | A plan was created in the pending area that is an orphan or standalone. |
| Repair Text: | From Oracle doc: Create plan directives if needed. Otherwise, delete the plan. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29375 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | sum of percentages %s for level %s, plan %s exceeds %s |
| Long Text: | The sum of percentages for the specified plan, level exceeds 100. |
| Repair Text: | From Oracle doc: Alter the percentages for the level so that they sum to 100. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29376 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of consumer groups %s in top-plan %s exceeds %s |
| Long Text: | The number of consumer groups in the specified top-plan is more than 32. |
| Repair Text: | From Oracle doc: Change the top-plan to have no more than 32 consumer groups. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29377 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | consumer group %s is not part of top-plan %s |
| Long Text: | OTHER_GROUPS was not included as part of the specified top-plan. Each top plan must include the built-in consumer group OTHER_GROUPS. |
| Repair Text: | From Oracle doc: Create a plan directive with the argument GROUP_OR_SUBPLAN being OTHER_GROUPS somewhere in the top-plan. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29379 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resource plan %s is involved in a loop in top-plan %s |
| Long Text: | A loop was discovered while validating a top-plan. |
| Repair Text: | From Oracle doc: Check the plans that have the specified plan as a GROUP_OR_SUBPLAN, and remove the plan directive that causes the loop. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29380 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | resource plan %s is currently active and cannot be deleted |
| Long Text: | An attempt was made to delete an active plan in the pending area. No changes can be made to active plans. |
| Repair Text: | From Oracle doc: Delete the plan when it is not in use. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29381 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | plan/consumer_group %s referred to by another plan and cannot be deleted |
| Long Text: | An attempt was made to delete a plan or consumer group that is referred to by another plan. |
| Repair Text: | From Oracle doc: Remove all plan directives that have the plan or consumer group as GROUP_OR_SUBPLAN; then delete the plan or consumer group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29382 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | validation of pending area failed |
| Long Text: | Invalid changes were attempted in the pending area. |
| Repair Text: | From Oracle doc: See documentation and the error messages that follow this one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29383 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | all leaves of top-plan %s must be consumer groups |
| Long Text: | An attempt was made to create or modify the specified top-plan but it has some plans as leaves. |
| Repair Text: | From Oracle doc: To identify which plans and/or plan directives need to be modified, look at all plans that have no plan directives. Then, alter the top-plan so that all its leaves are consumer groups. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29384 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of children for plan %s exceeds %s |
| Long Text: | An attempt was made to create or modify the specified plan, but the plan has more than 32 children. |
| Repair Text: | From Oracle doc: Make sure the specified plan points to no more than 32 distinct nodes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29385 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create plan directive from %s to %s |
| Long Text: | An attempt was made to create a plan directive from a plan to itself. |
| Repair Text: | From Oracle doc: Make sure the arguments PLAN and GROUP_OR_SUBPLAN to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER are different. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29386 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | plan or consumer group %s is mandatory and cannot be deleted or modified |
| Long Text: | An attempt was made to delete or modify the specified mandatory plan or consumer group. |
| Repair Text: | From Oracle doc: Do not attempt to delete or modify mandatory plans and consumer groups. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29387 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no top-plans found in the pending area |
| Long Text: | The VALIDATE_PENDING_AREA procedure found that either the intended top-plan(s) are involved in a loop or there are no top-plans. |
| Repair Text: | From Oracle doc: Check all edges going from a subplan to the intended top-plan. Make sure the top plan does not have any plan referring to it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29388 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | plan/consumer_group %s is part of more than one top-plan |
| Long Text: | An attempt was made to delete a subtree that includes a plan or consumer group that is part of more than one top-plan as part of procedure DELETE_PLAN_CASCADE or package DBMS_RESOURCE_MANAGER. Such a plan or consumer group cannot be deleted. |
| Repair Text: | From Oracle doc: Check the ancestors of the plan or consumer group and make sure it is only part of the top-plan that includes the subtree being deleted. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29389 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | too many errors during validation |
| Long Text: | The number of errors detected during validation is too high. |
| Repair Text: | From Oracle doc: Perform the necessary actions to remove some errors, and retry validation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29390 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | some resource plans are not part of any top-plan |
| Long Text: | An attempt was made to create or modify some plans in the pending area that are not part of any top-plan. |
| Repair Text: | From Oracle doc: Remove these plans are try validation again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29391 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s and %s must be mandatory to create a mandatory plan directive |
| Long Text: | An attempt was made to create a mandatory plan directive where either PLAN or GROUP_OR_SUBPLAN or both were not mandatory. |
| Repair Text: | From Oracle doc: Re-create these objects as mandatory and then create the plan directive. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29393 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user %s does not exist or is not logged on |
| Long Text: | An invalid user name was specified as argument to procedure SET_INITIAL_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER or SWITCH_CONSUMER_GROUP_FOR_USER of package DBMS_SYSTEM or the specified user was not logged on. |
| Repair Text: | From Oracle doc: Specify a valid user name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29394 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | session id %s and serial# %s do not exist |
| Long Text: | Invalid session id and serial# were specified as arguments to procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package DBMS_SYSTEM. |
| Repair Text: | From Oracle doc: Specify valid values from the view V$SESSION. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29395 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot set the initial consumer group to %s |
| Long Text: | An attempt was made to set the initial consumer group of a user to OTHER_GROUPS. |
| Repair Text: | From Oracle doc: OTHER_GROUPS is for the resource manager's internal use. Specify another consumer group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29396 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot switch group to %s |
| Long Text: | An attempt was made to switch the consumer group of a user or a session to OTHER_GROUPS. |
| Repair Text: | From Oracle doc: OTHER_GROUPS is for the resource manager's internal use. Specify another consumer group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29397 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot grant/revoke switch privilege for %s |
| Long Text: | An attempt was made to grant or revoke the privilege to switch to OTHER_GROUPS. |
| Repair Text: | From Oracle doc: OTHER_GROUPS is for the resource manager's internal use. Specify another consumer group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29398 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid privilege name specified |
| Long Text: | An invalid privilege name was specified as an argument to procedure GRANT_SYSTEM_PRIVILEGE or REVOKE_SYSTEM_PRIVILEGE of package DBMS_RESOURCE_MANAGER_PRIVS. |
| Repair Text: | From Oracle doc: Specify a valid privilege name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29399 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | user %s does not have privilege to switch to consumer group %s |
| Long Text: | An attempt was made to set the initial consumer group of the specified user but the user does not have the privilege to switch to that group. |
| Repair Text: | From Oracle doc: Grant the privilege to switch to the consumer group to the user and then set the initial group. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29400 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | data cartridge error%s |
| Long Text: | An error has occurred in a data cartridge external procedure. This message will be followed by a second message giving more details about the data cartridge error. |
| Repair Text: | From Oracle doc: See the Oracle8i Data Cartridge Developer's Guide for an explanation of the second error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NAMED keyword is invalid in CREATE JAVA CLASS |
| Long Text: | A NAMED keyword was specified in the CREATE JAVA CLASS statement. NAMED keywords are valid only in CREATE JAVA SOURCE or RESOURCE statements. |
| Repair Text: | From Oracle doc: Remove the NAMED keyword from the CREATE JAVA CLASS statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or missing Java source, class, or resource name |
| Long Text: | The required name for a Java source, class, or resource was invalid or missing. |
| Repair Text: | From Oracle doc: Specify a valid name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NAMED keyword required in CREATE JAVA RESOURCE |
| Long Text: | The name for a Java resource was not specified. The name must be specified with the NAMED keyword. |
| Repair Text: | From Oracle doc: Specify a valid name with the NAMED keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SCHEMA keyword not valid with NAMED keyword |
| Long Text: | SCHEMA and NAMED keywords were used together in the same CREATE JAVA command, but only one may be used in a CREATE JAVA command. |
| Repair Text: | From Oracle doc: Remove either the NAMED or the SCHEMA keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid or missing schema name |
| Long Text: | The required schema name was invalid or missing. |
| Repair Text: | From Oracle doc: Specify a valid schema name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | AS keyword is invalid in CREATE JAVA CLASS or RESOURCE |
| Long Text: | The AS keyword was used in CREATE JAVA CLASS or RESOURCE. The AS keyword is valid only in CREATE JAVA SOURCE. |
| Repair Text: | From Oracle doc: Use the USING keyword in CREATE JAVA CLASS or RESOURCE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid query derived from USING clause |
| Long Text: | The USING clause did not form a valid query. |
| Repair Text: | From Oracle doc: Correct the USING clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | query derived from USING clause found zero or many rows |
| Long Text: | The USING clause defined a query that either did not return any values, or returned more than one value. |
| Repair Text: | From Oracle doc: Correct the USING clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | query derived from USING clause did not select a value of type %s |
| Long Text: | The USING clause did not form a query that selects a value of the type specified by the term following the USING keyword. |
| Repair Text: | From Oracle doc: Correct the USING clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrectly formed Java binary class definition |
| Long Text: | An attempt was made to create a Java class using data expected to be in binary (Java .class) format. The data was found not to be in this format, or to be incorrectly formed. |
| Repair Text: | From Oracle doc: Correct the definition data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name, %s.%s, already used by an existing object |
| Long Text: | A CREATE JAVA command attempted to create a source, class, or resource object with a name that is already in use. |
| Repair Text: | From Oracle doc: Drop the existing object that is using the desired name, or use a different name for the new object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not resolve Java class |
| Long Text: | A CREATE AND RESOLVE NOFORCE JAVA CLASS command specified definition data that could not be resolved, or resolution failed for some referenced class. |
| Repair Text: | From Oracle doc: Remove the NOFORCE option or remove impediments to resolution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrectly formed name resolver specification |
| Long Text: | A name resolver was not specified in the required form: (( name_pattern , schema_name) ...). |
| Repair Text: | From Oracle doc: Correct the specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referenced class name too long |
| Long Text: | An attempt was made to import a .class file containing a class name of length greater than number. The .class file could not be imported because the referenced class name was too long. |
| Repair Text: | From Oracle doc: Shorten the referenced class name in the .class file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | class name contains illegal character |
| Long Text: | An attempt was made to import a .class file containing a character that cannot be converted to the server character set. The .class file could not be imported because of the illegal character. |
| Repair Text: | From Oracle doc: Correct the illegal character in the .class file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29515 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | exit called from Java code with status %s |
| Long Text: | Java code included a call to java.lang.Runtime.exitInternal. |
| Repair Text: | From Oracle doc: Do not include this call unless non-local exit is desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29516 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Aurora assertion failure: %s |
| Long Text: | An internal error occurred in the Aurora module. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29517 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | recursive resolution failed for a referenced class |
| Long Text: | An attempt to resolve a referenced class failed. |
| Repair Text: | From Oracle doc: Review the errors for referenced classes and complete the necessary actions to correct them. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29518 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name %s resolved to an object in schema %s that is not a Java class |
| Long Text: | A referenced name was resolved to an object that is not a Java class. |
| Repair Text: | From Oracle doc: Adjust name resolver or add missing Java class. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29519 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name %s resolved via a synonym in schema %s to a class with a different name |
| Long Text: | A referenced name was resolved to a synonym, which translated to a class whose name does not match the referenced name. |
| Repair Text: | From Oracle doc: Adjust name resolver or add missing Java class. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29520 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | name %s resolved to a class in schema %s that could not be accessed |
| Long Text: | An attempt to access a referenced class failed. |
| Repair Text: | From Oracle doc: Adjust authorizations or name resolution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29521 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referenced name %s could not be found |
| Long Text: | Name resolution failed to find an object with the indicated name. |
| Repair Text: | From Oracle doc: Adjust name resolver or add missing Java class. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29522 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | authorization error for referenced name %s.%s |
| Long Text: | An attempt was made to resolve a class that is not authorized to use the indicated referenced class. |
| Repair Text: | From Oracle doc: Adjust authorizations or name resolution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29523 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | authorization error for unknown referenced name |
| Long Text: | An attempt was made to resolve a class that is not authorized to use a referenced class. The name of the referenced class could not be determined. |
| Repair Text: | From Oracle doc: Adjust authorizations or name resolution. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29524 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | wrong types of arguments in call to '%s' |
| Long Text: | A method was called with argument(s) of incompatible type(s). |
| Repair Text: | From Oracle doc: Adjust caller. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29525 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referenced name is too long: '%s' |
| Long Text: | An attempt was made to create a class that references a name longer than 4000 characters. The class could not be created because the name is too long. |
| Repair Text: | From Oracle doc: Adjust the definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29526 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | created Java class %s"%s" |
| Long Text: | An informational message, not an error. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29527 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | created Java source %s"%s" |
| Long Text: | An informational message, not an error. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29528 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid Java call in trigger %s |
| Long Text: | The Java method specified in trigger does not exist or cannot be called as used. |
| Repair Text: | From Oracle doc: Adjust trigger definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29529 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid function or method call %s in trigger %s |
| Long Text: | The function or method specified in Java trigger call expression could not be resolved. |
| Repair Text: | From Oracle doc: Adjust trigger definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29530 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not create shortened name for %s |
| Long Text: | Insert into shortened name translation table failed. |
| Repair Text: | From Oracle doc: Retry the insert. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29531 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no method %s in class %s |
| Long Text: | An attempt was made to execute a non-existent method in a Java class. |
| Repair Text: | From Oracle doc: Adjust the call or create the specified method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29532 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Java call terminated by uncaught Java exception: %s |
| Long Text: | A Java exception or error was signaled and could not be resolved by the Java code. |
| Repair Text: | From Oracle doc: Modify Java code, if this behavior is not intended. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29533 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | attempt to overwrite class or resource %s while defining or compiling %s.%s |
| Long Text: | A class or resource defined by a SQLJ source conflicted with an existing object. |
| Repair Text: | From Oracle doc: Remove existing object, or modify SQLJ source. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29534 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referenced object %s.%s could not be resolved |
| Long Text: | Name resolution determined that the indicated object is referenced but could not be resolved. |
| Repair Text: | From Oracle doc: Correct name resolver or address resolution problems in the referenced class, or correct compilation problems in its source. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29535 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | source requires recompilation |
| Long Text: | The reason the current class object was invalid is recorded with the source object from which it was compiled. |
| Repair Text: | From Oracle doc: Inspect errors in the source object and take the necessary corrective actions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29536 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | badly formed source: %s |
| Long Text: | An attempt was made to create a Java source object with text that could not be parsed adequately to determine the class(es) defined by it. |
| Repair Text: | From Oracle doc: Correct errors in source. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29537 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | class or resource cannot be created or dropped directly |
| Long Text: | An attempt was made to create or drop a Java class or resource that is known to result from compilation of an existing Java source object. |
| Repair Text: | From Oracle doc: Act on the class or resource by acting on the source, or change the source so that it no longer defines the class or resource. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29538 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Java not installed |
| Long Text: | An attempt was made to use a Java command when Java is not installed. |
| Repair Text: | From Oracle doc: Install Java, or do not use the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29539 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Java system classes already installed |
| Long Text: | An attempt was made to use the CREATE JAVA SYSTEM command in a database where the Java system classes already are installed. |
| Repair Text: | From Oracle doc: Use CREATE OR REPLACE JAVA SYSTEM. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29540 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | class %s does not exist |
| Long Text: | Java method execution failed to find a class with the indicated name. |
| Repair Text: | From Oracle doc: Correct the name or add the missing Java class. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29541 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | class %s.%s could not be resolved |
| Long Text: | An attempt was made to execute a method in a Java class that had not been previously and cannot now be compiled or resolved successfully. |
| Repair Text: | From Oracle doc: Adjust the call or make the class resolvable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29542 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | class %s already defined by source %s |
| Long Text: | An attempt was made to create a Java source object that would define a class that is already defined by a different Java source object. |
| Repair Text: | From Oracle doc: Either drop the old source or modify the new source. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29543 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Java command %s not yet implemented |
| Long Text: | An attempt was made to use a Java command that is not yet implemented. |
| Repair Text: | From Oracle doc: Do not use the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29544 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid type |
| Long Text: | The type argument in a call to a Java export or import command did not have a recognized value. |
| Repair Text: | From Oracle doc: Correct the value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29545 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | badly formed class: %s |
| Long Text: | An attempt was made to create a Java class object with bytecodes that were rejected by the Java verifier. |
| Repair Text: | From Oracle doc: It is possible that an attempt was made to create the Java class from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using "-" in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29546 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | badly formed resource: %s |
| Long Text: | An attempt was made to create a Java resource object with data that was rejected by the Java verifier. |
| Repair Text: | From Oracle doc: Correct the data. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29547 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Java system class not available: %s |
| Long Text: | An attempt was made to use a command that requires a Java system class that was not yet present or was invalid. |
| Repair Text: | From Oracle doc: Load the system classes, or do not use the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29548 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Java system class reported: %s |
| Long Text: | A command that uses a Java system class was aborted due to an error reported by the Java system class. |
| Repair Text: | From Oracle doc: Correct the error that was reported. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29549 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | class %s.%s has changed, Java session state cleared |
| Long Text: | A class in use by the current session was redefined or dropped, invalidating the current Java session state and requiring that it be cleared. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29550 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | Java session state cleared |
| Long Text: | The Java state in the current session became inconsistent and was cleared. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not convert %s to Unicode |
| Long Text: | A string in the database character set could not be converted to Unicode, as required for use by Java. |
| Repair Text: | From Oracle doc: Correct the string. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | verification warning: %s |
| Long Text: | An attempt was made to create a Java class object with bytecodes that caused the Java verifier to issue a warning. |
| Repair Text: | From Oracle doc: It is possible that the Java class was created from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using "-" in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29553 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | class in use: %s.%s |
| Long Text: | An attempt was made to modify a Java class that is in use in the current call. |
| Repair Text: | From Oracle doc: Correct the code in use in this call. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29554 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | unhandled Java out of memory condition |
| Long Text: | The session encountered an out of memory condition in Java from which it could not recover. Java session state was cleared. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29555 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Java source, class or resource is not allowed here |
| Long Text: | A Java source, class, or resource was specified in an inappropriate place in a statement. |
| Repair Text: | From Oracle doc: Make sure the name is correct or remove it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29701 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to connect to Cluster Manager |
| Long Text: | Connect to the Cluster Manager (CM) failed or timed out. |
| Repair Text: | From Oracle doc: Verify that the CM was started. If the CM was not started, start it and then retry the database startup. If the CM died or is not responding, check the Oracle and CM trace files for errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29702 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred in Cluster Group Service operation |
| Long Text: | An unexpected error occurred while performing a CGS operation. |
| Repair Text: | From Oracle doc: Verify that the LMON process is still active. Also, check the Oracle LMON trace files for errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29703 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred in DLM operation |
| Long Text: | An unexpected error occurred while performing a DLM operation. |
| Repair Text: | From Oracle doc: Check Oracle trace files for errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29704 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release |
| Long Text: | The ACTIVE_INSTANCE_COUNT parameter was specified when one of the instances in the cluster was running Oracle 8.1.5 or an earlier release. |
| Repair Text: | From Oracle doc: Restart the instance without specifying the ACTIVE_INSTANCE_COUNT parameter. Or, upgrade all instances to Oracle 8.1.6 or later release and then specify the parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29705 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ACTIVE_INSTANCE_COUNT is %s but needs to be %s to be compatible |
| Long Text: | The value of the ACTIVE_INSTANCE_COUNT parameter must be the same in all Oracle Parallel Server instances. |
| Repair Text: | From Oracle doc: Check your initialization parameter files in all instances and ensure that the ACTIVE_INSTANCE_COUNT parameter has the same value. Then restart the instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29706 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect value %s for parameter ACTIVE_INSTANCE_COUNT |
| Long Text: | The ACTIVE_INSTANCE_COUNT parameter must be set to 1 in a two node active/standby parallel server configuration or to a value that is greater than or equal to the total number of instances if a standby instance is not needed. |
| Repair Text: | From Oracle doc: Check your initialization parameter files and correct the value of the ACTIVE_INSTANCE_COUNT parameter. If you are configuring a two node active/standby parallel server, set this value to 1. Otherwise, do not specify any value for the parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29800 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid name for operator |
| Long Text: | The name specified for the operator is incorrect. |
| Repair Text: | From Oracle doc: Specify a correct name for the operator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29801 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing RETURN keyword |
| Long Text: | The RETURN keyword has not been specified. |
| Repair Text: | From Oracle doc: Specify the RETURN keyword or check the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29802 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing CONTEXT keyword |
| Long Text: | The CONTEXT keyword has not been specified. |
| Repair Text: | From Oracle doc: Specify the CONTEXT keyword or check the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29803 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing ANCILLARY keyword |
| Long Text: | The ANCILLARY keyword has not been specified. |
| Repair Text: | From Oracle doc: Specify the ANCILLARY keyword or check the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29804 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing DATA keyword |
| Long Text: | The DATA keyword has not been specified. |
| Repair Text: | From Oracle doc: Specify the DATA keyword or check the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29805 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing COLUMN keyword |
| Long Text: | Keyword COLUMN is expected. |
| Repair Text: | From Oracle doc: Either specify the COLUMN keyword or specify another option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29806 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified binding does not exist |
| Long Text: | The operator binding which has been specified does not exist. |
| Repair Text: | From Oracle doc: Ensure that the operator binding that has been specified does exist. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29807 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified operator does not exist |
| Long Text: | The operator which has been specified does not exist. |
| Repair Text: | From Oracle doc: Ensure that the operator that has been specified does exist. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29808 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified primary operator binding does not exist |
| Long Text: | The specified binding for the primary operator does not exist. |
| Repair Text: | From Oracle doc: Ensure that the specified binding for the primary operator exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29809 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop an operator with dependent objects |
| Long Text: | The operator which is being dropped has some dependent objects. |
| Repair Text: | From Oracle doc: Either drop the dependent objects first and then issue the DROP OPERATOR command or specify the FORCE option with DROP OPERATOR. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29810 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inadequate operator privileges |
| Long Text: | The user does not have the appropriate privileges to perform the specified operation on the operator. |
| Repair Text: | From Oracle doc: Grant the appropriate privileges to the user and then reissue the statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29811 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing STATISTICS keyword |
| Long Text: | This is not a valid option with the ASSOCIATE command. |
| Repair Text: | From Oracle doc: Specify STATISTICS keyword after the ASSOCIATE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29812 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | incorrect object name specified |
| Long Text: | The specified name is not a valid name. |
| Repair Text: | From Oracle doc: Specify the correct name of the object with for which an association needs to be defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29813 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-supported object type with associate statement |
| Long Text: | The type of object specified is not supported with the associate statistics statement. |
| Repair Text: | From Oracle doc: Use a valid object type with the associate command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29814 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | expecting USING or DEFAULT keyword |
| Long Text: | Expecting the USING or DEFAULT keyword after the names of object(s). |
| Repair Text: | From Oracle doc: Provide the USING or DEFAULT keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29815 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object being associated is not present |
| Long Text: | The object for which the association is being defined is not present. |
| Repair Text: | From Oracle doc: Ensure that all the objects for which the association is being defined are present. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29816 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object being disassociated is not present |
| Long Text: | Object which is being disassociated is not present. |
| Repair Text: | From Oracle doc: Ensure that the object which needs to be disassociated is present. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29817 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | non-supported option with disassociate statement |
| Long Text: | The type of object specified is not supported with the disassociate statistics statement. |
| Repair Text: | From Oracle doc: Use a object type which is supported with the disassociate command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29818 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column name not properly specified |
| Long Text: | Name of the column should contain the table and the column name. |
| Repair Text: | From Oracle doc: Specify a valid column name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29819 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot associate default values with columns |
| Long Text: | An attempt was made to associate DEFAULT values with columns which is not a valid option. |
| Repair Text: | From Oracle doc: Specify a valid option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29820 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the statistics type is not present |
| Long Text: | The statistics type which is being associated with object(s) is not present. |
| Repair Text: | From Oracle doc: Ensure that the type which contains the statistics functions is present. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29821 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified primary operator does not exist |
| Long Text: | The specified primary operator does not exist. |
| Repair Text: | From Oracle doc: Check the primary operator and the signature specified. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29822 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | selectivity cannot be specified for the type of object |
| Long Text: | An attempt was made to associate selectivity with index or index types which is not allowed. |
| Repair Text: | From Oracle doc: Specify a valid option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29823 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object being analyzed is not a table |
| Long Text: | The object being analyzed is not a table and is not supported. |
| Repair Text: | From Oracle doc: Specify only a supported option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29824 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operator is invalid |
| Long Text: | The operator is invalid. |
| Repair Text: | From Oracle doc: Drop and re-create the operator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29825 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid name for indextype |
| Long Text: | Index type name or index type schema name has invalid characters. |
| Repair Text: | From Oracle doc: Verify that the name has valid characters and it is not a reserved word. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29826 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword FOR is missing |
| Long Text: | FOR keyword must be provided with CREATE INDEXTYPE statement. |
| Repair Text: | From Oracle doc: Use FOR keyword and provide relevant operator information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29827 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword USING is missing |
| Long Text: | USING keyword and corresponding implementation details must be provided. |
| Repair Text: | From Oracle doc: Provide USING keyword and relevant implementation details with CREATE INDEXTYPE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29828 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid name for implementation type |
| Long Text: | Implementation type or Implementation schema name is invalid. |
| Repair Text: | From Oracle doc: Verify that the name has valid characters and it is not a reserved word. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29829 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | implementation type does not exist |
| Long Text: | The implementation type specified with USING clause could not be found. |
| Repair Text: | From Oracle doc: Check to see if the type exists and the user has EXECUTE privilege on this type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29830 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operator does not exist |
| Long Text: | The operator could not be found. |
| Repair Text: | From Oracle doc: Verify that the operator exists and the user has EXECUTE privilege for this operator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29831 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operator binding not found |
| Long Text: | The specified binding for the operator is not available from the operator schema object. |
| Repair Text: | From Oracle doc: Verify that the operator with the specified binding exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29832 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot drop or replace an indextype with dependent indexes |
| Long Text: | One or more indexes are dependent upon the index type. |
| Repair Text: | From Oracle doc: Drop all the indexes which are dependent upon the index type before dropping the index type itself. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29833 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | indextype does not exist |
| Long Text: | There is no index type by the specified name. |
| Repair Text: | From Oracle doc: Use public views for the index types to see if an index type by the specified name has been created. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29834 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REF datatype not supported with operators |
| Long Text: | The user specified a REF datatype which is not supported in CREATE OPERATOR. |
| Repair Text: | From Oracle doc: Reissue the CREATE OPERATOR statement without the REF datatype. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29835 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ODCIGETINTERFACES routine does not return required interface(s) |
| Long Text: | The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the interface(s) required by the current usage. |
| Repair Text: | From Oracle doc: Ensure that the ODCIGetInterfaces routine returns the name(s) of the required interface(s). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29836 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to validate referenced operators |
| Long Text: | One of the operators referenced cannot be compiled. |
| Repair Text: | From Oracle doc: Try to recompile the operators which are referenced by this index type. Use USER_INDEXTYPE_OPERATORS view to find out the referenced operators. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29837 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to execute implementation type |
| Long Text: | User does not have privileges to execute the implementation type. |
| Repair Text: | From Oracle doc: The owner of the implementation type must grant appropriate privileges to the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29838 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to execute the operator(s) |
| Long Text: | User does not have privileges to execute one of the operators. |
| Repair Text: | From Oracle doc: The owner of the operators must grant appropriate privileges to the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29839 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to validate implementation type for the indextype |
| Long Text: | Implementation type for the index type cannot be compiled. |
| Repair Text: | From Oracle doc: Try to compile the implementation type which is specified for this index type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29840 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | indextype and implementation type are not in same schema |
| Long Text: | Index type and implementation type are in different schema. |
| Repair Text: | From Oracle doc: Put the index type and implementation type in the same schema. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29850 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid option for creation of domain indexes |
| Long Text: | The user specified an invalid option like ASC, DESC, SORT or a parallel clause, partitioning clause or physical attributes clause. |
| Repair Text: | From Oracle doc: Choose one of the valid clauses for creation of domain indexes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29851 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot build a domain index on more than one column |
| Long Text: | User attempted to build a domain index on more than one column. |
| Repair Text: | From Oracle doc: Build the domain index only on a single column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29852 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword IS is missing |
| Long Text: | IS keyword must be specified with Create Index statement for domain indexes. |
| Repair Text: | From Oracle doc: Use IS keyword and then specify the index type name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29853 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword UNIQUE may not be used in creating domain indexes |
| Long Text: | An attempt was made to create a domain index with the UNIQUE attribute. |
| Repair Text: | From Oracle doc: Remove UNIQUE from the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29854 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | keyword BITMAP may not be used in creating domain indexes |
| Long Text: | An attempt was made to create a domain index with the BITMAP attribute. |
| Repair Text: | From Oracle doc: Remove BITMAP from the CREATE INDEX statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29855 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred in the execution of ODCIINDEXCREATE routine |
| Long Text: | Failed to successfully execute the ODCIIndexCreate routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29856 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred in the execution of ODCIINDEXDROP routine |
| Long Text: | Failed to successfully execute the ODCIIndexDrop routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29857 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | domain indexes and/or secondary objects exist in the tablespace |
| Long Text: | An attempt was made to drop a tablespace which contains secondary objects and/or domain indexes. |
| Repair Text: | From Oracle doc: Drop the domain indexes in his tablespace. Also, find the domain indexes which created secondary objects in this tablespace and drop them. Then try dropping the tablespace. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29858 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred in the execution of ODCIINDEXALTER routine |
| Long Text: | Failed to successfully execute the ODCIIndexAlter routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29859 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error occurred in the execution of ODCIINDEXTRUNCATE routine |
| Long Text: | Failed to successfully execute the ODCIIndexTruncate routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29860 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot truncate a table with domain indexes marked LOADING |
| Long Text: | The table has domain indexes defined on it that are marked LOADING. |
| Repair Text: | From Oracle doc: Wait to see if the ongoing index DDL ends and the index state changes from LOADING state. Else, drop the domain indexes marked as LOADING with the FORCE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29861 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | domain index is marked LOADING/FAILED/UNUSABLE |
| Long Text: | An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful ODCIIndexCreate or is marked unusable by a DDL operation. |
| Repair Text: | From Oracle doc: Wait if the specified index is marked LOADING Drop the specified index if it is marked FAILED Drop or rebuild the specified index if it is marked UNUSABLE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29862 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify FORCE option for dropping non-domain index |
| Long Text: | A DROP INDEX FORCE was issued for a non-domain index. |
| Repair Text: | From Oracle doc: Reissue the command without the FORCE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29863 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | warning in the execution of ODCIINDEXCREATE routine |
| Long Text: | A warning was returned from the ODCIIndexCreate routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly Check user specified log tables for greater detail. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29864 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | analyzing domain indexes marked LOADING/FAILED not supported |
| Long Text: | An attempt was made to analyze a domain index which was marked as LOADING or FAILED. |
| Repair Text: | From Oracle doc: If the index was marked LOADING, wait till it is marked valid before retrying the analyze. If index was marked FAILED, drop it OR rebuild it and retry the analyze. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29865 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | indextype is invalid |
| Long Text: | The index type is invalid. |
| Repair Text: | From Oracle doc: Drop and re-create the index type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29866 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create domain index on a column of index-organized table |
| Long Text: | An attempt was made to create a domain index on a column of an index-organized table. |
| Repair Text: | From Oracle doc: Do not attempt to create a domain index on columns of an index-organized table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29867 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a domain index on a LONG column |
| Long Text: | The user attempted to create a domain index on a column of LONG datatype. |
| Repair Text: | From Oracle doc: Do not create a domain index on a LONG column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29868 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | cannot issue DDL on a domain index marked as LOADING |
| Long Text: | An attempt was made to issue a DROP/ALTER/TRUNCATE on a domain index in a LOADING state. |
| Repair Text: | From Oracle doc: Wait till the index operation completes OR issue a DROP INDEX FORCE to drop the index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29869 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot issue ALTER without REBUILD on a domain index marked FAILED |
| Long Text: | An attempt was made to ALTER a domain index in FAILED state. |
| Repair Text: | From Oracle doc: Truncate the table to mark the index as valid and then issue a ALTER INDEX OR do ALTER INDEX REBUILD to rebuild the index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29870 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified options are only valid for altering a domain index |
| Long Text: | Specified the ONLINE or PARAMETERS clause with a non-domain index. |
| Repair Text: | From Oracle doc: Reissue the statement with the correct syntax for alter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29871 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid alter option for a domain index |
| Long Text: | The user specified an invalid option for altering a domain index. |
| Repair Text: | From Oracle doc: Reissue the alter statement with a valid option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29872 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameters clause cannot be combined with the specified options |
| Long Text: | The user combined PARAMETERS clause with other alter index options. |
| Repair Text: | From Oracle doc: Reissue the statement with the correct syntax for alter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29873 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | warning in the execution of ODCIINDEXDROP routine |
| Long Text: | A warning was returned from the ODCIIndexDrop routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly Check the user defined warning log tables for greater details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29874 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | warning in the execution of ODCIINDEXALTER routine |
| Long Text: | A warning was returned from the ODCIIndexAlter routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly Check the user defined warning log tables for greater details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29875 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed in the execution of the ODCIINDEXINSERT routine |
| Long Text: | Failed to successfully execute the ODCIIndexInsert routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29876 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed in the execution of the ODCIINDEXDELETE routine |
| Long Text: | Failed to successfully execute the ODCIIndexDelete routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29877 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed in the execution of the ODCIINDEXUPDATE routine |
| Long Text: | Failed to successfully execute the ODCIIndexUpdate routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29878 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | warning in the execution of ODCIINDEXTRUNCATE routine |
| Long Text: | A warning was returned from the ODCIIndexTruncate routine. |
| Repair Text: | From Oracle doc: Check to see if the routine has been coded correctly. Check the user defined warning log tables for greater details. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29879 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create multiple domain indexes on a column list using same indextype |
| Long Text: | An attempt was made to define multiple domain indexes on the same column list using identical indextypes. |
| Repair Text: | From Oracle doc: Check to see if a different indextype can be used or if the index can be defined on another column list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29880 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | such column list already indexed using another domain index and indextype |
| Long Text: | An attempt was made to create multiple domain indexes on a column list using indextypes which do not have disjoint operators. |
| Repair Text: | From Oracle doc: Check to see if the operator sets for the indextypes can be made disjoint. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29881 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | failed to validate indextype |
| Long Text: | Index type cannot be compiled. |
| Repair Text: | From Oracle doc: Try to compile the index type which is referenced by the domain index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29882 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | insufficient privileges to execute indextype |
| Long Text: | User does not have privileges to execute the index type. |
| Repair Text: | From Oracle doc: The owner of the index type must grant appropriate privileges to the user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29883 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create a domain index on column expressions |
| Long Text: | User specified an expression in the column list. |
| Repair Text: | From Oracle doc: Specify only simple columns in the column list for domain index. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29884 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | domain index is defined on the column to be dropped |
| Long Text: | An ALTER TABLE DROP COLUMN was issued on a column on which a domain index exists. |
| Repair Text: | From Oracle doc: Drop the domain index before attempting to drop the column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29885 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | domain index is defined on the column to be modified |
| Long Text: | An ALTER TABLE MODIFY COLUMN was issued on a column on which a domain index exists. |
| Repair Text: | From Oracle doc: Drop the domain index before attempting to modify the column. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29886 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | feature not supported for domain indexes |
| Long Text: | Feature is not supported for domain indexes. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29887 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot support row movement if domain index defined on table |
| Long Text: | An ALTER TABLE ENABLE ROW MOVEMENT was issued on a table which has a domain index defined on it. |
| Repair Text: | From Oracle doc: Drop the domain index if you want to enable row movement and then reissue the command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29888 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create domain index on a table with row movement enabled |
| Long Text: | A CREATE DOMAIN INDEX statement was issued on a table that has row movement enabled. |
| Repair Text: | From Oracle doc: Disable the row movement in the table and then reissue the create domain index statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29900 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | operator binding does not exist |
| Long Text: | There is no binding for the current usage of the operator. |
| Repair Text: | From Oracle doc: Change the operator arguments to match any of the existing bindings or add a new binding to the operator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29901 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function underlying operator binding does not exist |
| Long Text: | The function underlying the operator binding does not exist. |
| Repair Text: | From Oracle doc: Ensure that the function corresponding to the operator invocation exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29902 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in executing ODCIIndexStart() routine |
| Long Text: | The execution of ODCIIndexStart routine caused an error. |
| Repair Text: | From Oracle doc: Examine the error messages produced by the index type code and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29903 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in executing ODCIIndexFetch() routine |
| Long Text: | The execution of ODCIIndexFetch routine caused an error. |
| Repair Text: | From Oracle doc: Examine the error messages produced by the index type code and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29904 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in executing ODCIIndexClose() routine |
| Long Text: | The execution of ODCIIndexClose routine caused an error. |
| Repair Text: | From Oracle doc: Examine the error messages produced by the index type code and take appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29905 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | method %s does not exist in type %s.%s |
| Long Text: | A required method with the required signature does not exist in the specified type. |
| Repair Text: | From Oracle doc: Add the required method to the type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29906 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | indextype %s.%s does not exist |
| Long Text: | The index type does not exist. |
| Repair Text: | From Oracle doc: Create the index type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29907 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | found duplicate labels in primary invocations |
| Long Text: | There are multiple primary invocations of operators with the same number as the label. |
| Repair Text: | From Oracle doc: Use distinct labels in primary invocations. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29908 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing primary invocation for ancillary operator |
| Long Text: | The primary invocation corresponding to an ancillary operator is missing. |
| Repair Text: | From Oracle doc: Add the primary invocation with the same label as the ancillary operator. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29909 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | label for the ancillary operator is not a literal number |
| Long Text: | The label used for invoking the ancillary operator is not a literal number. |
| Repair Text: | From Oracle doc: Use a literal number as the label. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29910 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid callback operation |
| Long Text: | Encountered an invalid callback operation. |
| Repair Text: | From Oracle doc: Ensure that all the callbacks executed from callouts are valid in the statement context. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29911 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | null scan context returned by ODCIIndexStart() routine |
| Long Text: | The ODCIIndexStart() routine returned a null scan context. |
| Repair Text: | From Oracle doc: Ensure that the ODCIIndexStart() routine returns a non-null scan context. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29925 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot execute %s |
| Long Text: | The specified function does not exist or does not have an appropriate signature. |
| Repair Text: | From Oracle doc: Implement the function with the appropriate signature. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29926 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | association already defined for the object |
| Long Text: | The object for which the association is being defined, already has a statistics type associated with it. |
| Repair Text: | From Oracle doc: Disassociate the object and then associate the object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29927 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error in executing the ODCIStatsCollect / ODCIStatsDelete routine |
| Long Text: | The ODCIStatsCollect/ODCIStatsDelete function is causing an error. |
| Repair Text: | From Oracle doc: Check the ODCIStatsCollect/ODCIStatsDelete function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29928 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate default selectivity specified |
| Long Text: | The keyword DEFAULT SELECTIVITY can only be specified once. |
| Repair Text: | From Oracle doc: Remove the duplicate keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29929 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing SCAN Keyword |
| Long Text: | The scan context is not specified. |
| Repair Text: | From Oracle doc: Supply the SCAN keyword. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29930 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause |
| Long Text: | The COMPUTE ANCILLARY DATA option was specified without the WITH INDEX CONTEXT clause. |
| Repair Text: | From Oracle doc: Specify the WITH INDEX CONTEXT option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29931 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified association does not exist |
| Long Text: | One or more of the object(s) that have been specified to be disassociated, do not have an association defined for them. |
| Repair Text: | From Oracle doc: Verify the objects which have an association defined and issue the disassociate command again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29932 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the type being dropped is a statistics type |
| Long Text: | Some objects have defined their statistics methods in the type being dropped. |
| Repair Text: | From Oracle doc: First drop the relevant associations using the DISASSOCIATE command and then retry the DROP command, or use the FORCE option with DROP TYPE command. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29933 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object being disassociated has some user defined statistics stored |
| Long Text: | There are some user-defined statistics collected for the object being disassociated. |
| Repair Text: | From Oracle doc: First delete the user-defined statistics and then reissue the DISASSOCIATE command or specify the FORCE option with DISASSOCIATE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29934 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index specified for association is not a domain index |
| Long Text: | The user issued an ASSOCIATE STATISTICS command with an index which is not a domain index. |
| Repair Text: | From Oracle doc: Issue an ASSOCIATE STATISTICS WITH INDEXES command on a domain index only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-29935 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing FROM keyword |
| Long Text: | The keyword FROM is missing. |
| Repair Text: | From Oracle doc: Specify the FROM keyword or check the SQL statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30000 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing either trim specification or char expression in TRIM |
| Long Text: | Since FROM is specified in TRIM function, either trim specification (TRAILING, HEADING, BOTH) or trim character or both must be specified. |
| Repair Text: | From Oracle doc: Add either trim specification (TRAILING, HEADING, BOTH) or trim character or both. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30001 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | trim set should have only one character |
| Long Text: | Trim set contains more or less than 1 character. This is not allowed in TRIM function. |
| Repair Text: | From Oracle doc: Change trim set to have only 1 character. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30071 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | conversion between datetime/interval and %s fail |
| Long Text: | An error occurred during a conversion between datetime/interval and string data type due to one of the following reasons: The buffer is too short to hold the result. The format string is bad. |
| Repair Text: | From Oracle doc: Correct the problem and try again. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30072 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid time zone value |
| Long Text: | The value specified for the time zone string, which appears in ALTER SESSION statement, environment variable ORA_SDTZ, or a datetime factor, is not valid. |
| Repair Text: | From Oracle doc: Specify a valid time zone value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30073 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid adjustment value |
| Long Text: | The value is none of the followings: 'ADJUST', 'NO_ADJUST', 'ANSI_DATE', 'ADJUST_WITH_ANSI_DATE'. 'NO_ADJUST' is the default value. |
| Repair Text: | From Oracle doc: Set it to one of the three values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30074 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed |
| Long Text: | An attempt was made to GLOBAL partition an index on TIME/TIMESTAMP WITH TIME ZONE. |
| Repair Text: | From Oracle doc: Do not GLOBAL partition an index on TIME/TIMESTAMP WITH TIME ZONE. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30075 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint |
| Long Text: | An attempt was made to create a constraint on a time or timestamp with or without time zone column without explicitly specifying the time zone. |
| Repair Text: | From Oracle doc: Use time or timestamp with time zone literals only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30076 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid extract field for extract source |
| Long Text: | The extract source does not contain the specified extract field. |
| Repair Text: | From Oracle doc: Specify a valid extract field for the extract source. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30077 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | illegal casting between specified datetime types |
| Long Text: | Cannot cast between the specified datetime types. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30078 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals |
| Long Text: | An attempt was made to use a time/timestamp expression whose format does not explicitly have time zone on a TIME/TIMESTAMP WITH TIME ZONE column. |
| Repair Text: | From Oracle doc: Explicitly use the TIME/TIMESTAMP WITH TIME ZONE literal. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30080 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | evaluation of NUMTOYMINTERVAL or NUMTODSINTERVAL failed |
| Long Text: | None. |
| Repair Text: | From Oracle doc: None. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30081 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid data type for datetime/interval arithmetic |
| Long Text: | The data types of the operands are not valid for datetime/interval arithmetic. |
| Repair Text: | From Oracle doc: Specify valid data types for datetime/interval arithmetic. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30082 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datetime/interval column to be modified must be empty to decrease fractional second or leading field precision |
| Long Text: | Datetime/interval column with existing data is being modified to decrease fractional second or leading field precisions. |
| Repair Text: | From Oracle doc: Such columns are only allowed to increase the precisions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30083 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | syntax error was found in interval value expression |
| Long Text: | A syntax error was found during parsing an interval value expression. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30084 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid data type for datetime primary with time zone modifier |
| Long Text: | When a time zone modifier is specified, the data type of datetime primary must be one of the following: TIME, TIME WITH TIME ZONE, TIMESTAMP, TIMESTAMP WITH TIME ZONE. |
| Repair Text: | From Oracle doc: Specify a valid data type. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30085 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | syntax error was found in overlaps predicate |
| Long Text: | A syntax error was found during parsing an overlaps predicate. |
| Repair Text: | From Oracle doc: Correct the syntax. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30086 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | interval year-month result not allowed for datetime subtraction |
| Long Text: | An attempt was made to specify interval year to month as the result of datetime subtraction. |
| Repair Text: | From Oracle doc: This is not allowed currently due to unclear specification in SQL Standards for this interval type. Change the interval type to interval day to second and resubmit statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30087 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Adding two datetime values is not allowed |
| Long Text: | An attempt was made to add two datetime values. |
| Repair Text: | From Oracle doc: This addition is not allowed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30088 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | datetime/interval precision is out of range |
| Long Text: | The specified datetime/interval precision was not between 0 and 9. |
| Repair Text: | From Oracle doc: Use a value between 0 and 9 for datetime/interval precision. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30089 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing or invalid datetime_field |
| Long Text: | A datetime_field (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is expected but not found, or a datetime_field specified the end_field in an interval_qualifier is more significant than its start_field. |
| Repair Text: | From Oracle doc: Specify a valid datetime field. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30100 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error [number] |
| Long Text: | An internal error has occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support and report the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unknown parameter name '%s' |
| Long Text: | You have misspelled the parameter name. |
| Repair Text: | From Oracle doc: Spell the parameter name correctly. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s' is not in the legal range for '%s' |
| Long Text: | The value of the parameter is not within the legal range. |
| Repair Text: | From Oracle doc: Refer to Oracle8i SQL Reference for the allowable values for this parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30103 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s' contains an illegal integer radix for '%s' |
| Long Text: | An illegal integer radix specification was found. |
| Repair Text: | From Oracle doc: Only 'd', 'h', 'D', and 'H' may be used as radix specifications. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30104 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s' is not a legal integer for '%s' |
| Long Text: | The value is not a valid integer. |
| Repair Text: | From Oracle doc: Specify only valid integers for this parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s' is not a legal boolean for '%s' |
| Long Text: | The value is not a valid boolean. |
| Repair Text: | From Oracle doc: Refer to Oracle8i SQL Reference for allowable boolean values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30106 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30107 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | parameter name abbreviation '%s' is not unique |
| Long Text: | The abbreviation given was not unique. |
| Repair Text: | From Oracle doc: Use a longer abbreviation to make the parameter name unique. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30108 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid positional parameter value '%s' |
| Long Text: | An invalid positional parameter value has been entered. |
| Repair Text: | From Oracle doc: Remove the invalid positional parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30109 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | could not open parameter file '%s' |
| Long Text: | The parameter file does not exist. |
| Repair Text: | From Oracle doc: Create an appropriate parameter file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30110 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error at '%s' |
| Long Text: | A syntax error was detected. |
| Repair Text: | From Oracle doc: Change the input so that the correct syntax is used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30111 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no closing quote for value '%s' |
| Long Text: | A quoted string was begun but not finished. |
| Repair Text: | From Oracle doc: Put a closing quote in the proper location. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30112 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | multiple values not allowed for parameter '%s' |
| Long Text: | An attempt was made to specify multiple values for a parameter which can take only one value. |
| Repair Text: | From Oracle doc: Do not specify more than one value for this parameter. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30113 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error when processing file '%s' |
| Long Text: | A problem occurred when processing this file. |
| Repair Text: | From Oracle doc: Examine the additional error messages and correct the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30114 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error when processing from command line |
| Long Text: | A problem occurred when processing the command line. |
| Repair Text: | From Oracle doc: Examine the additional error messages and correct the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30115 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | error when processing an environment variable |
| Long Text: | A problem occurred when processing an environment variable. |
| Repair Text: | From Oracle doc: Examine the additional error messages and correct the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30116 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error at '%s' following '%s' |
| Long Text: | A syntax error was detected. |
| Repair Text: | From Oracle doc: Change the input so that the correct syntax is used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30117 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error at '%s' at the start of input |
| Long Text: | A syntax error was detected. |
| Repair Text: | From Oracle doc: Change the input so that the correct syntax is used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30118 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | syntax error at '%s' at the end of input |
| Long Text: | A syntax error was detected. |
| Repair Text: | From Oracle doc: Change the input so that the correct syntax is used. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30119 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to obtain a valid value for '%s' |
| Long Text: | No valid value was obtained for this parameter. |
| Repair Text: | From Oracle doc: Rerun the application and enter a valid value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30120 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s' is not a legal oracle number for '%s' |
| Long Text: | The value is not a valid Oracle number. |
| Repair Text: | From Oracle doc: Refer to Oracle8i SQL Reference for allowable Oracle number values. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30121 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid function argument received |
| Long Text: | A function received an invalid argument |
| Repair Text: | From Oracle doc: Check function calls, make sure correct arguments are being passed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30122 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid parameter key type received |
| Long Text: | A function received an invalid parameter key type. |
| Repair Text: | From Oracle doc: Check parameter key types in function calls. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30123 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of keys being set exceeds allocation |
| Long Text: | Number of parameter keys being set exceeds allocation. |
| Repair Text: | From Oracle doc: Reduce the number of keys being set or increase allocation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30124 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid key index supplied |
| Long Text: | The key index specified was not within bounds. |
| Repair Text: | From Oracle doc: Change key index to ensure it lies within bounds. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30125 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30135 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCI Thread operation fails |
| Long Text: | An OCI Thread function call has failed. |
| Repair Text: | From Oracle doc: Check the function call to make sure that the correct parameters are being passed and take the appropriate action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30150 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Invalid argument passed to OCIFile function |
| Long Text: | An invalid argument is passed to the OCIFile function. The most common cause is that a NULL pointer is passed where a non-NULL pointer is expected. |
| Repair Text: | From Oracle doc: Make sure that the values passed as arguments are valid. Check for NULL pointers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30151 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File already exists |
| Long Text: | An attempt was made to open a file with OCI_FILE_EXCL flag and the file already exists. |
| Repair Text: | From Oracle doc: OCIFile is supposed throw this exception in this case. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30152 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | File does not exist |
| Long Text: | The OCIFile function requires the file to exist, but it does not. |
| Repair Text: | From Oracle doc: Make sure that the file exists. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30153 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | An invalid File Object is passed to the OCIFile function |
| Long Text: | An invalid File Object is passed to the OCIFile function. |
| Repair Text: | From Oracle doc: Make sure that the file object is a valid one. Create a new file object by calling OCIFileOpen if needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30154 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The memory address given as buffer for OCIFileRead/Write is invalid |
| Long Text: | An invalid memory address is given as the buffer pointer for OCIFileRead/Write. |
| Repair Text: | From Oracle doc: Make sure that the required memory is allocated and pass a valid memory address as buffer pointer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30155 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | An I/O Error occured during an OCIFile function call |
| Long Text: | An I/O error occurred at the system level. |
| Repair Text: | From Oracle doc: This is a system error and the action will depend on the error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30156 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Out of disk space |
| Long Text: | The disks associated with the underlying file system are full. |
| Repair Text: | From Oracle doc: Create more disk space. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30157 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | An invalid argument was given to operating system call |
| Long Text: | The operating system call was called with an invalid argument. |
| Repair Text: | From Oracle doc: Check the values passed. If you are unable to solve the problem, contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30158 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The OCIFileWrite causes the file to exceed the maximum allowed size |
| Long Text: | There is no space to write to the file. Its size is at the maximum limit. |
| Repair Text: | From Oracle doc: If you can, increase the limit. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30159 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | OCIFileOpen: Cannot create the file or cannot open in the requested mode |
| Long Text: | The create flag was specified in OCIFileOpen such that the file was to be created. But unable to do so. Or the file already exists and the permissions on it does not allow the file to be opened in the requested open mode. |
| Repair Text: | From Oracle doc: Check whether the user has permissions to create the specified file or if the file exists whether the permissions on it allow the requested open mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30160 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to access the file |
| Long Text: | The function was unable to access the existing the file. |
| Repair Text: | From Oracle doc: Check if the user has the required permissions on the file. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30161 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | A system error occurred during the OCIFile function call |
| Long Text: | A system error occurred while executing the OCIFile function. |
| Repair Text: | From Oracle doc: Investigate and solve the system error. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30162 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The OCIFile context is not initialzed |
| Long Text: | The function OCIFileInit need to be called before calling any other OCIFile function to initialize the OCIFile context. |
| Repair Text: | From Oracle doc: Call the function OCIFileInit need to be called before calling any other OCIFile function. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30163 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The thread safety initialization failed |
| Long Text: | The call to SlgInit failed in OCIFileInit. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30175 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid type given for an argument |
| Long Text: | There is an argument with an invalid type in the argument list. |
| Repair Text: | From Oracle doc: Use the correct type wrapper for the argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30176 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid format code used in the format %s |
| Long Text: | There is an invalid format code in the format string. |
| Repair Text: | From Oracle doc: Replace the invalid format code with a valid one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30177 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid flag used in a format specification |
| Long Text: | There is an invalid flag in a format specification. |
| Repair Text: | From Oracle doc: Replace the invalid flag with a valid one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30178 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate flag used in a format specification |
| Long Text: | There is a duplicate flag in a format specification. |
| Repair Text: | From Oracle doc: Remove the duplicate flag. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30179 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid argument index used in a format code |
| Long Text: | Zero or negative argument index or index not following (. |
| Repair Text: | From Oracle doc: Replace the invalid argument index with a valid one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30180 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument index is too large |
| Long Text: | An argument index exceeds actual number of arguments supplied. |
| Repair Text: | From Oracle doc: Fix format string or pass additional arguments. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30181 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | integer in argument index is not immediately followed by ) |
| Long Text: | Missing closing parenthesis in argument index. |
| Repair Text: | From Oracle doc: Fix the format specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30182 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid precision specifier |
| Long Text: | Period in format specification not followed by valid format. |
| Repair Text: | From Oracle doc: Replace the invalid precision specifier with a valid one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30183 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid field width specifier |
| Long Text: | Invalid field width supplied. |
| Repair Text: | From Oracle doc: Replace the invalid field width with a valid one. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30184 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | argument type not compatible with a format code |
| Long Text: | Bad argument type given for a format code. |
| Repair Text: | From Oracle doc: Make format and arguments be compatible. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30185 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | output too large to fit in the buffer |
| Long Text: | The buffer is not large enough to hold the entire output string. |
| Repair Text: | From Oracle doc: Fix the buffer size and length passed in. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30186 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30187 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30188 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30189 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30190 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30191 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | missing argument list |
| Long Text: | No argument list supplied. |
| Repair Text: | From Oracle doc: Modify the argument list to have at least OCIFormatEnd in it. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30192 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30193 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30194 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30195 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30196 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30197 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30198 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30199 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | reserved for future use |
| Long Text: | This message is reserved for future use. |
| Repair Text: | From Oracle doc: No action required. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Wrong NLS item was passed into OCINlsGetInfo() |
| Long Text: | The item is not supported NLS item. |
| Repair Text: | From Oracle doc: Correct the item number passed to OCINlsGetInfo(). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30201 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unable to load NLS data object |
| Long Text: | It may be caused by invalid NLS environment setting. |
| Repair Text: | From Oracle doc: Check your NLS environment setting such as ORA_NLS33. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30202 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NULL pointer to OCIMsgh was passed to OCIMsg function |
| Long Text: | The NULL pointer was passed. |
| Repair Text: | From Oracle doc: Check the value of the OCIMsgh pointer. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30203 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Cannot open mesage file |
| Long Text: | The message may not exist in your system. |
| Repair Text: | From Oracle doc: Check the message for the given product and facility. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30331 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | summary does not exist |
| Long Text: | A non-existent summary name was specified. |
| Repair Text: | From Oracle doc: Check the spelling of the summary name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30332 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | container table already in use by other summary |
| Long Text: | Another summary is already using this table as a container table. |
| Repair Text: | From Oracle doc: Select another table or snapshot as the container table for this summary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30333 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dimension does not exist |
| Long Text: | The dimension named in a dimension DDL statement does not exist. |
| Repair Text: | From Oracle doc: Check the spelling of the dimension name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30334 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal dimension level name |
| Long Text: | A level name in a dimension DDL statement did not conform to SQL identifier rules. |
| Repair Text: | From Oracle doc: Use a level name that begins with a letter, consists of only letters, digits, and underscores and contains no more than 30 characters. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30335 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | JOIN KEY clause references a level not in this hierarchy |
| Long Text: | The level name specified with the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not reference a level in the hierarchy that contains the JOIN KEY clause. |
| Repair Text: | From Oracle doc: Check the spelling of the level name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30336 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no child for specified JOIN KEY |
| Long Text: | The level specified in the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not have a child level. |
| Repair Text: | From Oracle doc: Check the spelling of the level name referenced in the JOIN KEY clause. If the referenced level is the first level in the hierarchy, you need not and must not specify a JOIN KEY clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30337 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | multiple JOIN KEY clauses specified for the same parent level |
| Long Text: | More than one JOIN KEY clause was specified for a given parent level in a dimension hierarchy. |
| Repair Text: | From Oracle doc: Match up each JOIN KEY clause with the level it references in the hierarchy. Eliminate the redundant JOIN KEY clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30338 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal dimension hierachy name |
| Long Text: | An illegal dimension hierarchy name was specified in a dimension DDL statement. |
| Repair Text: | From Oracle doc: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30339 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal dimension attribute name |
| Long Text: | An illegal dimension attribute name was specified in a dimension DDL statement. |
| Repair Text: | From Oracle doc: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30340 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | illegal dimension name |
| Long Text: | An illegal dimension name was specified in a dimension DDL statement. |
| Repair Text: | From Oracle doc: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30341 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dropped level has references |
| Long Text: | An attempt was made to drop a level using the default or RESTRICT option in a dimension while references to that level remain in the dimension. References can occur in hierarchies and attributes within the dimension. |
| Repair Text: | From Oracle doc: First remove any references to the level prior to dropping it, or specify the CASCADE option with the DROP LEVEL clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30342 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referenced level is not defined in this dimension |
| Long Text: | A reference to a level not defined within the dimension was found. |
| Repair Text: | From Oracle doc: Check the spelling of the level name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30343 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | level name is not unique within this dimension |
| Long Text: | Two or more levels were defined with the same name. |
| Repair Text: | From Oracle doc: Check the spelling of the level names. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30344 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | number of child cols different from number of parent level cols |
| Long Text: | The number of child columns specified in a JOIN KEY clause is not the same as the number of columns in the specified parent level. |
| Repair Text: | From Oracle doc: Check the child columns and the columns in the definition of the referenced parent level and correct the discrepancy. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30345 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | circular dimension hierarchy |
| Long Text: | A circularity was found the dimension hierarchy. |
| Repair Text: | From Oracle doc: Check the hierarchy for a level name that occurs more than once. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30346 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | hierarchy name must be unique within a dimension |
| Long Text: | The same name was used for more than one hierarchy in a dimension. |
| Repair Text: | From Oracle doc: Check the spelling of the hierarchy name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30347 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a table name is required to qualify the column specification |
| Long Text: | A table name was omitted in a column specification where the column must be qualified by the table name. |
| Repair Text: | From Oracle doc: Qualify the column with the table name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30348 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ADD and DROP cannot both be specified |
| Long Text: | One or more ADD clauses were found in the same ALTER DIMENSION statement with one or more DROP clauses. |
| Repair Text: | From Oracle doc: Separate your ADD operations into one ALTER DIMENSION statement and your DROP operations into another. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30349 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified dimension hierarchy does not exist |
| Long Text: | A hierarchy name was encountered that is not defined within the dimension. |
| Repair Text: | From Oracle doc: Check the spelling of the hierarchy name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30350 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | specified dimension attribute does not exist |
| Long Text: | An attribute name was encountered that is not defined within the dimension. |
| Repair Text: | From Oracle doc: Check the attribute name spelling. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30351 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | query rewrite does not currently support this expression |
| Long Text: | A complex expression was specified that is not currently supported by query rewrite. |
| Repair Text: | From Oracle doc: Reduce the complexity of the expression. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30352 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | inconsistent numeric precision or %s length |
| Long Text: | The SELECT expression was of a different numeric precision or string length than the corresponding container column. Therefore, query rewrite cannot guarantee results that are identical to the results obtained with the un-rewritten query. |
| Repair Text: | From Oracle doc: Correct the precision or string length difference, specify the WITH REDUCED PRECISION option, or disable the REWRITE option on the materialized view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30353 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | expression not supported for query rewrite |
| Long Text: | The select clause referenced UID, USER, ROWNUM, SYSDATE, CURRENT_TIMESTAMP, MAXVALUE, a sequence number, a bind variable, correlation variable, a set result, a trigger return variable, a parallel table queue column, collection iterator, and so on. |
| Repair Text: | From Oracle doc: Remove the offending expression or disable the REWRITE option on the materialized view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30354 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Query rewrite not allowed on SYS relations |
| Long Text: | A SYS relation was referenced in the select clause for a materialized view with query rewrite enabled. |
| Repair Text: | From Oracle doc: Remove the reference to the SYS relation from the select clause or disable the REWRITE option on the materialized view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30355 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | materialized view container does not exist |
| Long Text: | A DROP TABLE command was issued directly against the materialized view container table. |
| Repair Text: | From Oracle doc: Use the DROP MATERIALIZED VIEW command to clean up the residual metadata for the materialized view. Then use the CREATE MATERIALIZED VIEW statement to re-create the materialized view. Thereafter, use the DROP MATERIALIZED VIEW command rather than the DROP TABLE command to drop a materialized view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30356 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | the specified refresh method is not supported in this context |
| Long Text: | The refresh method that was specified is not currently supported. |
| Repair Text: | From Oracle doc: Specify a different refresh method or change the context to enable support of the chosen refresh method. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30357 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this PL/SQL function cannot be supported for query rewrite |
| Long Text: | The statement referenced a PL/SQL function that is not marked DETERMINISTIC. |
| Repair Text: | From Oracle doc: Perform one of the following actions: Remove the use of the PL/SQL function. Mark the PL/SQL function as DETERMINISTIC. Disable the REWRITE option on the materialized view. The function should be marked DETERMINISTIC only if it always returns the same result value for any given set of input argument values, regardless of any database state or session state. Do not mark the function as DETERMINISTIC if it has any meaningful side-effects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30358 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | summary and materialized view are not in same schema |
| Long Text: | An internal error occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30359 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Query rewrite is not supported on SYS materialized views |
| Long Text: | An attempt was made to enable the REWRITE option on a materialized view in the SYS schema. |
| Repair Text: | From Oracle doc: Create the materialized view in a different schema or disable the REWRITE option. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30360 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | REF not supported with query rewrite |
| Long Text: | The statement contained a REF operator. Repeatable behavior cannot be guaranteed with the REF operator. Therefore, query rewrite cannot support the REF operator. |
| Repair Text: | From Oracle doc: Remove the reference to the REF operator or disable the REWRITE option on the materialized view. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30361 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unrecognized %s type |
| Long Text: | An internal error occurred. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30362 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | dimension column cannot be a sequence |
| Long Text: | The dimension statement referenced a column that is a sequence. |
| Repair Text: | From Oracle doc: Remove the reference to the sequence. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30363 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | columns in a dimension column list must be in the same relation |
| Long Text: | The dimension statement contained a column list where the columns are not all from the same relation. |
| Repair Text: | From Oracle doc: Specify the list of columns using only columns from a single relation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30364 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | this level has the same set of columns as another |
| Long Text: | The level definition contained the same set of columns as another level. |
| Repair Text: | From Oracle doc: Eliminate the redundant level definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30365 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | left relation in the JOIN KEY clause cannot be same as right |
| Long Text: | The relation of the child columns on the left side of the JOIN KEY clause was the same as that of the parent level on the right side. |
| Repair Text: | From Oracle doc: Remove the JOIN KEY clause. It is not required or allowed when the child and the parent are in the same relation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30366 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | child JOIN KEY columns not in same relation as child level |
| Long Text: | The relation of the child columns on the left side of the JOIN KEY clause differed from that of that child level. |
| Repair Text: | From Oracle doc: Specify the correct child columns in the JOIN KEY clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30367 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | a JOIN KEY clause is required |
| Long Text: | A JOIN KEY clause was omitted in a dimension statement. A JOIN KEY clause is required when the child level and the parent level are not in the same relation. |
| Repair Text: | From Oracle doc: Specify a JOIN KEY clause to indicate how the relation of the child level joins to the relation of the parent level. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30368 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ATTRIBUTE cannot determine column in a different relation |
| Long Text: | An ATTRIBUTE clause in a dimension statement specified a determined column on the right that is in a different relation than that of the level on the left. |
| Repair Text: | From Oracle doc: Specify attributes only for those dimension levels that functionally determine other columns within the same relation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30369 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of columns is 32 |
| Long Text: | A list of columns was specified using more than 32 columns. |
| Repair Text: | From Oracle doc: Specify the list using no more than 32 columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30370 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | set operators are not supported in this context |
| Long Text: | A set operator such as UNION, UNION ALL, INTERSECT, or MINUS was encountered in an unsupported context, such as in a materialized view definition. |
| Repair Text: | From Oracle doc: Re-specify the expression to avoid the use of set operators. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30371 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | column cannot define a level in more than one dimension |
| Long Text: | A column was used in the definition of a level after it had already been used to define a level in a different dimension. |
| Repair Text: | From Oracle doc: Reorganize dimension levels and hierarchies into a single dimension such that no column is used to define levels in different dimensions. There is no limit on the number of levels or hierarchies you can place in a dimension. A column can be used to define any number of levels provided all such levels are in the same dimension and provided no two levels contain identical sets of columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30372 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | fine grain access policy conflicts with materialized view |
| Long Text: | A fine grain access control procedure has applied a non-null policy to the query for the materialized view. |
| Repair Text: | From Oracle doc: In order for the materialized view to work correctly, any fine grain access control procedure in effect for the query must return a null policy when the materialized view is being created or refreshed. This may be done by ensuring that the usernames for the creator, owner, and invoker of refresh procedures for the materialized view all receive a null policy by the user-written fine grain access control procedures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30373 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | object data types are not supported in this context |
| Long Text: | An object data type was encountered in an unsupported context, such as in a materialized view definition. |
| Repair Text: | From Oracle doc: Re-specify the expression to avoid the use of objects. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30430 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | list does not contain any valid summaries |
| Long Text: | List is empty or does not contain the names of existing summaries. |
| Repair Text: | From Oracle doc: Verify that the list of names passed to refresh contains the name of at least one existing summary object |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30431 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh method must be ANY or INCREMENTAL or FORCE_FULL, not %s |
| Long Text: | An invalid refresh method was specified. |
| Repair Text: | From Oracle doc: Verify that the refresh method is one of 'ANY' or 'INCREMENTAL' or 'FORCE_FULL'. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30432 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | summary '%s.%s' is in INVALID state |
| Long Text: | The summary is in INVALID state and cannot be refreshed. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30433 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s.%s' is not a summary |
| Long Text: | There is no such summary, therefore it cannot be refreshed. |
| Repair Text: | From Oracle doc: Verify the correct name of the summary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30434 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh method must be one of FC?AN, not '%s' |
| Long Text: | An invalid refresh method was specified. |
| Repair Text: | From Oracle doc: Verify that the refresh method is one of 'FC?AN'. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30435 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | job_queue_processes must be non-zero in order to refresh summaries |
| Long Text: | The server must be started with parameter JOB_QUEUE_PROCESSES greater than zero. |
| Repair Text: | From Oracle doc: Correct the value of JOB_QUEUE_PROCESSES and restart the server instance. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30436 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to open named pipe '%s' |
| Long Text: | The refresh process was unable to open a named pipe to the job queue process usually because of insufficient system resources. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30437 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | all job queue processes have stopped running |
| Long Text: | All of the job queue processes used by refresh have stopped for some reason. At least one job queue process must be running in order to refresh summaries. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30438 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to access named pipe '%s' |
| Long Text: | The refresh process was unable to access a named pipe to the job queue process after it successfully opened the pipe. This usually indicates an internal or operating system error condition. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30439 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh of '%s.%s' failed because of %s |
| Long Text: | The refresh job queue process encountered an error and is reporting it. The accompanying text of the message indicates cause of the error. |
| Repair Text: | From Oracle doc: Varies, depending upon the reported cause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30450 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | refresh_after_errors was TRUE, and one or more errors occurred |
| Long Text: | One or more errors occurred during a refresh of multiple summaries. |
| Repair Text: | From Oracle doc: The NUMBER_OF_FAILURES parameter returns the count of how many failures occurred. The trace logs for each refresh operation describe the each individual failure in more detail. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30451 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | internal error |
| Long Text: | An internal error was detected by the summary refresh subsystem, and aborted the refresh operation. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30452 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X) |
| Long Text: | Incremental refresh of summaries requires a COUNT(X) column in order to incrementally refresh AVG(X). It requires both SUM(X) and COUNT(X) columns in order to in refresh STDDEV(X) or VARIANCE(X). |
| Repair Text: | From Oracle doc: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30453 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | summary contains AVG without corresponding COUNT |
| Long Text: | Incremental refresh of summaries with AVG(X) requires a COUNT(X) column to be included in the summary definition. |
| Repair Text: | From Oracle doc: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30454 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | summary contains STDDEV without corresponding SUM & COUNT |
| Long Text: | Incremental refresh of summaries with STDDEV(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition. |
| Repair Text: | From Oracle doc: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30455 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | summary contains VARIANCE without corresponding SUM & COUNT |
| Long Text: | Incremental refresh of summaries with VARIANCE(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition. |
| Repair Text: | From Oracle doc: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30456 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s.%s' cannot be refreshed because of insufficient privilege |
| Long Text: | The user lacks one or more permissions that are required in order to refresh summaries. |
| Repair Text: | From Oracle doc: Make sure that the user is granted all required privileges. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30457 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s.%s' cannot be refreshed because of unmnanaged NOT NULL columns in container |
| Long Text: | The container object for the summary contains one or more unmanaged columns do not allow nulls, and which do not specify a default value for those columns. |
| Repair Text: | From Oracle doc: Make sure that default values are specified for all NOT NULL columns that are not part of the summary definition. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30458 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s.%s' cannot be refreshed because the refresh mask is %s |
| Long Text: | An attempt was made to incrementally refresh a summary that is not incrementally refreshable. |
| Repair Text: | From Oracle doc: Do not attempt to incrementally refresh the summary; use full refresh instead. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30459 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s.%s' cannot be refreshed because the refresh method is NONE |
| Long Text: | An attempt was made to refresh a summary whose refresh method is NONE. |
| Repair Text: | From Oracle doc: Summaries whose refresh method is NONE (NEVER REFRESH) cannot be refreshed. Alter the summary to change the default refresh method from NONE to some other value. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30460 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s.%s' cannot be refreshed because it is marked UNUSABLE |
| Long Text: | An attempt was made to refresh a summary which is UNUSABLE. |
| Repair Text: | From Oracle doc: Determine why the summary is UNUSABLE, re-enable it, and retry the refresh. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30461 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s.%s' cannot be refreshed because it is marked DISABLED |
| Long Text: | An attempt was made to refresh a summary which is DISABLED. |
| Repair Text: | From Oracle doc: Determine why the summary is DISABLED, re-enable it, and retry the refresh. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30462 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unsupported operator: %s |
| Long Text: | An attempt was made to refresh a summary containing an unsupported operator. |
| Repair Text: | From Oracle doc: Verify that all columns of the summary contain expressions that are refreshable. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30463 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | '%s' is not a detail table of any summary |
| Long Text: | The list of tables passed to REFRESH_DEPENDENT contains at least one invalid table name. That table is not a detail table of any summary and is therefore an invalid input to REFRESH_DEPENDENT. |
| Repair Text: | From Oracle doc: Verify the correct name of all tables in the list. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30464 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | no summaries exist |
| Long Text: | A call was made to REFRESH_ALL_MVIEWS, but no summaries exist. At least one summary must exist before calling REFRESH_ALL_MVIEWS. |
| Repair Text: | From Oracle doc: Create one or more summaries. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30475 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | feature not enabled: %s |
| Long Text: | The specified feature is not enabled. |
| Repair Text: | From Oracle doc: Do not attempt to use this feature. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30476 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | PLAN_TABLE does not exist in the user's schema |
| Long Text: | Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN" command to estimate cardinality of the specified select-clause. This requires a table called the PLAN_TABLE in the user's schema. For more information, refer to Oracle8i SQL Reference. |
| Repair Text: | From Oracle doc: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most systems a script UTLXPLAN.SQL will create this table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30477 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | The input select_clause is incorrectly specified |
| Long Text: | The input select-clause parameter to Estimate_Summary_Size is incorrectly specified and cannot be compiled. |
| Repair Text: | From Oracle doc: Check the syntax of the select-clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30478 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Specified dimension does not exist |
| Long Text: | The specified dimension to be verified does not exist. |
| Repair Text: | From Oracle doc: Check the spelling of the dimension name. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30479 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Summary Advisor error%s |
| Long Text: | An error has occurred in the Summary Advisor package. This message will be followed by a second message giving more details about the nature of the error. |
| Repair Text: | From Oracle doc: See the Summary Advisor documentation for an explanation of the second error message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30480 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | DISTINCT option not allowed with GROUP BY CUBE or ROLLUP |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30481 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | GROUPING function only supported with GROUP BY CUBE or ROLLUP |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30500 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | database open triggers and server error triggers cannot have BEFORE type |
| Long Text: | An attempt was made to create a trigger that fires before the database is open or before server errors, but these types of triggers are not supported. |
| Repair Text: | From Oracle doc: Do not attempt to create a trigger that fires before the database is open or before server errors. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30501 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | instance shutdown triggers cannot have AFTER type |
| Long Text: | An attempt was made to create a trigger that fires after an instance shutdown, but this type of trigger is not supported. |
| Repair Text: | From Oracle doc: Do not attempt to create a trigger that fires after an instance shutdown. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30502 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system triggers cannot have INSERT, UPDATE, or DELETE as triggering events |
| Long Text: | An attempt was made to create a system trigger with INSERT, UPDATE, or DELETE triggering events, but this type of trigger is not supported because a system trigger does not have a base table. |
| Repair Text: | From Oracle doc: Do not attempt to create a system trigger with INSERT, UPDATE, or DELETE triggering events. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30503 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system triggers cannot have a REFERENCING clause |
| Long Text: | An attempt was made to use a REFERENCING clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table. |
| Repair Text: | From Oracle doc: Do not use a REFERENCING clause with a system trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30504 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system triggers cannot have a FOR EACH ROW clause |
| Long Text: | An attempt was made to use a FOR EACH ROW clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table. |
| Repair Text: | From Oracle doc: Do not use a FOR EACH ROW clause with a system trigger. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30505 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system triggers should not reference a column in a WHEN clause |
| Long Text: | An attempt was made to use a WHEN clause to reference a column with a system trigger, but this type of trigger is not supported because a system trigger does not have a base table. |
| Repair Text: | From Oracle doc: Change the WHEN clause to an appropriate clause. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30506 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system triggers cannot be based on tables or views |
| Long Text: | An attempt was made to base a system trigger on a table or a view. |
| Repair Text: | From Oracle doc: Make sure the type of the trigger is compatible with the base object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30507 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | normal triggers cannot be based on a schema or a database |
| Long Text: | An attempt was made to base a normal trigger on a schema or a database, but normal triggers can be based only on tables or views. |
| Repair Text: | From Oracle doc: Make sure the type of the trigger is compatible with the base object. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30508 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | client logon triggers cannot have BEFORE type |
| Long Text: | An attempt was made to create a trigger that fires before logon. This type of trigger is not supported. |
| Repair Text: | From Oracle doc: Do not attempt to create a trigger that fires before logon. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30509 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | client logoff triggers cannot have AFTER type |
| Long Text: | An attempt was made to create a trigger that fires after logoff. This type of trigger is not supported. |
| Repair Text: | From Oracle doc: Do not attempt to create a trigger that fires after logoff. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30510 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system triggers cannot be defined on the schema of SYS user |
| Long Text: | An attempt was made to define a system trigger on the schema of SYS user. This type of trigger is not supported currently. |
| Repair Text: | From Oracle doc: Do not attempt to create a system trigger defined on the schema of SYS user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30511 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | invalid DDL operation in system triggers |
| Long Text: | An attempt was made to perform an invalid DDL operation in a system trigger. Most DDL operations currently are not supported in system triggers. The only currently supported DDL operations are table operations and ALTER?COMPILE operations. |
| Repair Text: | From Oracle doc: Remove invalid DDL operations in system triggers. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30512 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot modify %s.%s more than once in a transaction |
| Long Text: | An attempt was made to modify an object more than once in a transaction. This error is usually caused by a DDL statement that fires a system trigger that tries to modify the same object. It can also happen when an attempt is made to perform more than one DDL operation on a queue table in the same transaction without issuing a commit between operations. |
| Repair Text: | From Oracle doc: Do not create system triggers that might modify an already modified object. Also, do not specify more than one DDL operation on a queue table in the same transaction. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30513 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot create system triggers of INSTEAD OF type |
| Long Text: | Only BEFORE or AFTER triggers can be created on system events. |
| Repair Text: | From Oracle doc: Change the trigger type to BEFORE or AFTER. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30514 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | system trigger cannot modify tablespace being made read only |
| Long Text: | A beofre trigger tries to modify a tablespace which is being made READ ONLY as the part of DDL oepration. |
| Repair Text: | From Oracle doc: Modify the trigger to avoid modifications to the objects in the same tablespace as the one which is being made read only, or use autonomous transactions to commit modifications. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30550 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | index depends on a package/function spec/body which is not valid |
| Long Text: | The functional indexes depend on some invalid/non-existent package/function specification/body. |
| Repair Text: | From Oracle doc: Verify that all the package/functions which the index depends on exist and are valid. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30551 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The index depends on a package/type body which does not exist |
| Long Text: | The functional indexes depend on a package/type body which does not exist. |
| Repair Text: | From Oracle doc: Create the package/type body. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30552 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The package/procedure/function cannot be changed |
| Long Text: | The package/procedure/function is deterministic and some object depends on it. |
| Repair Text: | From Oracle doc: Drop the other object which depends on the package/function/procedure you are trying to change. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30553 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The function is not deterministic |
| Long Text: | The function on which the index is defined is not deterministic. |
| Repair Text: | From Oracle doc: Mark the function deterministic. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30554 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | function-based index %s.%s is disabled |
| Long Text: | An attempt was made to access a function-based index that has been marked disabled because the function on which the index depends has been changed. |
| Repair Text: | From Oracle doc: Perform one of the following actions: drop the specified index using the DROP INDEX command rebuild the specified index using the ALTER INDEX REBUILD command enable the specified index using the ALTER INDEX ENABLE command make the specified index usable using the ALTER INDEX UNUSABLE command |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30555 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | global index partitioning key is an expression |
| Long Text: | An attempt was made to use an expression as a partitioning key in an index. |
| Repair Text: | From Oracle doc: Do not attempt to use an expression as index partitioning key. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30560 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SAMPLE option not allowed with index-organized tables |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30561 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SAMPLE option not allowed in statement with multiple table references |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30562 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | SAMPLE percentage must be in the range [0.000001,100) |
| Long Text: | No description available. |
| Repair Text: | From Oracle doc: No action defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30575 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ConText Option not installed |
| Long Text: | Oracle executable does not have ConText Option linked in. |
| Repair Text: | From Oracle doc: Get the correct version of Oracle. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30576 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | ConText Option dictionary loading error |
| Long Text: | ConText dictionary tables may be corrupted. This is an internal error. |
| Repair Text: | From Oracle doc: Contact Oracle Customer Support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30625 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | method dispatch on NULL SELF argument is disallowed |
| Long Text: | A member method of a type is being invoked with a NULL SELF argument. |
| Repair Text: | From Oracle doc: Change the method invocation to pass in a valid self argument. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30726 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify referenced column list here |
| Long Text: | An attempt was made to specify a referenced column list for a referential constraint involving a REF column. |
| Repair Text: | From Oracle doc: Remove the referenced column list specification. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30727 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | duplicate referential constraint for a REF column |
| Long Text: | Multiple referential constraints were specified for a single REF column. |
| Repair Text: | From Oracle doc: Remove the duplicate referential constraint and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30728 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of columns exceeded |
| Long Text: | Adding referential constraint on a REF column requires the creation of an additional column. |
| Repair Text: | From Oracle doc: Drop some columns and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30729 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | maximum number of columns exceeded |
| Long Text: | Adding scope or referential constraint on a REF column requires the creation of additional columns if the target table's object identifier is primary key based. |
| Repair Text: | From Oracle doc: Drop some columns and retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30730 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | referential constraint not allowed on nested table column |
| Long Text: | An attempt was made to define a referential constraint on a nested table column. |
| Repair Text: | From Oracle doc: Do not specify referential constraints on nested table columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30731 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | scope constraint not allowed on nested table column when the nested table is being created |
| Long Text: | An attempt was made to define a scope constraint on a nested table column when the nested table is being created. |
| Repair Text: | From Oracle doc: Do not specify a scope constraint on a nested table column when creating it. Instead, specify it using the ALTER TABLE statement. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30732 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | table contains no user-visible columns |
| Long Text: | An attempt was made to query on a system table which has no user-visible columns. |
| Repair Text: | From Oracle doc: Do not query on a system table that has no user-visible columns. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30733 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify rowid constraint on scoped ref column |
| Long Text: | An attempt was made to specify ROWID constraint on a scoped REF column. |
| Repair Text: | From Oracle doc: Remove the ROWID constraint and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30734 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | cannot specify scope constraint on ref column with rowid |
| Long Text: | An attempt was made to specify scope constraint on a REF column with the ROWID constraint. |
| Repair Text: | From Oracle doc: Remove the scope constraint and then retry the operation. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 140-30926 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | unable to get a stable set of rows in the source tables |
| Long Text: | A stable set of rows could not be got because of a large amount of DML activity or a non-deterministic where clause. |
| Repair Text: | From Oracle doc: Remove any non-deterministic where clauses and reissue the DML. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-9993 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages (/var/log/messages* files) for the reported time. If the result is a real problem save all the diagnostic Information and call for a technical support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-9994 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages (/var/log/messages* files) for the reported time. If the result is a real problem save all the diagnostic Information and call for a technical support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-9995 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages (/var/log/messages* files) for the reported time. If the result is a real problem save all the diagnostic Information and call for a technical support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-9996 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages (/var/log/messages* files) for the reported time. If the result is a real problem save all the diagnostic Information and call for a technical support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-9997 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages (/var/log/messages* files) for the reported time. If the result is a real problem save all the diagnostic Information and call for a technical support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-9999 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages (/var/log/messages* files) for the reported time. If the result is a real problem save all the diagnostic Information and call for a technical support. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10100 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | CAMPUS_DB: ASM diskgroup %s is %d%% full. |
| Long Text: | The free space of the ASM disk group is low. This may be caused by an unexpected growth of table spaces. |
| Repair Text: | Please check the size / fill level of the datafiles in that disk group (views: dba_data_files, dba_tablespaces, dba_segments). Check also if orphaned datafiles are present in the ASM diskgroup. Consider contacting the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10101 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | CAMPUS_DB: ASM diskgroup %s is %d%% full. |
| Long Text: | The free space of the ASM disk group is low. This may be caused by an unexpected growth of table spaces. |
| Repair Text: | Please check the size / fill level of the datafiles in that disk group (views: dba_data_files, dba_tablespaces, dba_segments). Check also if orphaned datafiles are present in the ASM diskgroup. Consider contacting the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10102 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CAMPUS_DB: ASM diskgroup %s is %d%% full. |
| Long Text: | The free space of the ASM disk group is low. This may be caused by an unexpected growth of table spaces. |
| Repair Text: | Please check the size / fill level of the datafiles in that disk group (views: dba_data_files, dba_tablespaces, dba_segments). Check also if orphaned datafiles are present in the ASM diskgroup. Consider contacting the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10103 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | CAMPUS_DB: ASM diskgroup %s has %d offline disks. |
| Long Text: | Some disks in the ASM disk groups are offline. The redundancy of the system is degraded. |
| Repair Text: | Analyse the system messages for possible reasons (e.g failures of the storage) and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10104 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | CAMPUS_DB: ASM diskgroup %s has %d offline disks. |
| Long Text: | Some disks in the ASM disk groups are offline. The redundancy of the system is degraded. |
| Repair Text: | Analyse the system messages for possible reasons (e.g failures of the storage) and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10105 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | CAMPUS_DB: ASM diskgroup %s has %d offline disks. |
| Long Text: | Some disks in the ASM disk groups are offline. The redundancy of the system is degraded. |
| Repair Text: | Analyse the system messages for possible reasons (e.g failures of the storage) and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10106 |
| Severity: | Normal |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10107 |
| Severity: | Normal |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10108 |
| Severity: | Warning |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10109 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10110 |
| Severity: | Critical |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10111 |
| Severity: | Critical |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s Fault - Cache Disabling, %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10112 |
| Severity: | Cleared |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s Host system cache enabled., %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10113 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s Storage Array Faulted %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10114 |
| Severity: | Cleared |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s Storage Array is not Faulted, %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10115 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s SPS Removed %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10116 |
| Severity: | Cleared |
| Event Type: | equipment alarm |
| Description: | EMC_Clariion: %s SPS Enabled, %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the messages on the clariion storage system and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10302 |
| Severity: | Minor |
| Event Type: | equipment alarm |
| Description: | FSC_SERVERCONTROL2: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10303 |
| Severity: | Minor |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10304 |
| Severity: | Normal |
| Event Type: | equipment alarm |
| Description: | FSC_SERVERCONTROL2: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10305 |
| Severity: | Warning |
| Event Type: | equipment alarm |
| Description: | FSC_SERVERCONTROL2: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10306 |
| Severity: | Minor |
| Event Type: | equipment alarm |
| Description: | FSC_SERVERCONTROL2: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10307 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | FSC_SERVERCONTROL2: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10308 |
| Severity: | Critical |
| Event Type: | equipment alarm |
| Description: | FSC_SERVERCONTROL2: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10309 |
| Severity: | Normal |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10310 |
| Severity: | Warning |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10311 |
| Severity: | Minor |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10312 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10313 |
| Severity: | Critical |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s |
| Long Text: | Please refer error text |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10314 |
| Severity: | Critical |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s Power supply failed |
| Long Text: | Power supply failed |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10315 |
| Severity: | Cleared |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s Power supply OK |
| Long Text: | Power supply OK |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10316 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s Power unit: power supply redundancy lost |
| Long Text: | Power unit: power supply redundancy lost |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10317 |
| Severity: | Cleared |
| Event Type: | equipment alarm |
| Description: | INTEL_WFM: %s Power unit: power supply redundancy available |
| Long Text: | Power unit: power supply redundancy available |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10320 |
| Severity: | Normal |
| Event Type: | equipment alarm |
| Description: | COMPAQ: %s |
| Long Text: | Please check the corresponding logging files of the system. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10321 |
| Severity: | Warning |
| Event Type: | equipment alarm |
| Description: | COMPAQ: %s |
| Long Text: | Please check the corresponding logging files of the system. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10322 |
| Severity: | Minor |
| Event Type: | equipment alarm |
| Description: | COMPAQ: %s |
| Long Text: | Please check the corresponding logging files of the system. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10323 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | COMPAQ: %s |
| Long Text: | Please check the corresponding logging files of the system. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10324 |
| Severity: | Critical |
| Event Type: | equipment alarm |
| Description: | COMPAQ: %s |
| Long Text: | Please check the corresponding logging files of the system. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10325 |
| Severity: | Normal |
| Event Type: | equipment alarm |
| Description: | COMPAQ: %s |
| Long Text: | Please check the corresponding logging files of the system. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10400 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | HPSmartArray: %s |
| Long Text: | One or more local disks connected to the RAID controller are not working correctly. The redundancy of the system is degraded. |
| Repair Text: | Analyse the state of the local disks connected to the RAID controller and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10401 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | RAID: %s |
| Long Text: | RAID Controller Error. |
| Repair Text: | Analyse the state of the local disks connected to the RAID controller and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10410 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | MegaRAID: %s |
| Long Text: | One or more local disks connected to the megaraid SAS controller are not working correctly. The redundancy of the system is degraded. |
| Repair Text: | Analyse the state of the local disks connected to the megaraid SAS controller and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10450 |
| Severity: | Minor |
| Event Type: | equipment alarm |
| Description: | Network Adapter: %s: Link is down |
| Long Text: | The link of a network adapter is down. |
| Repair Text: | The link of a network adapter is down. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10451 |
| Severity: | Cleared |
| Event Type: | equipment alarm |
| Description: | Network Adapter: %s: Link is up |
| Long Text: | The link of a network adapter is up. |
| Repair Text: | The link of a network adapter is up. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10452 |
| Severity: | Minor |
| Event Type: | equipment alarm |
| Description: | bonding: %s: the bonding link status of one adapter is down |
| Long Text: | The bonding link status of a network adapter is down. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10453 |
| Severity: | Major |
| Event Type: | equipment alarm |
| Description: | bonding: %s: the bonding link status of any(2) adapter is down |
| Long Text: | The bonding link status of any network adapter is down. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10454 |
| Severity: | Cleared |
| Event Type: | equipment alarm |
| Description: | bonding: %s: the bonding link status of one adaper is up |
| Long Text: | The bonding link status of a network adapter is up. |
| Repair Text: | Analyse the system messages for possible reasons and contact the support service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10455 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | Ignore this message. Only an info. |
| Long Text: | Ignore this message. Only an info. |
| Repair Text: | Ignore this message. Only an info. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-10456 |
| Severity: | Normal |
| Event Type: | indeterminate |
| Description: | Ignore this message. |
| Long Text: | Ignore this message. |
| Repair Text: | Ignore this message. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 141-20000 |
| Severity: | Warning |
| Event Type: | indeterminate |
| Description: | %s |
| Long Text: | This event is sent when an OS message could not be properly mapped to EVENT:<set>-<num> due to a short text difference in the RtpLogOs event catalogue. Please, check the details for event EVENT:<set>-<num> using RtpAdmCli or RTP GUI. |
| Repair Text: | The RtpLogOs event catalogue (RtpLogOsShortText.msg and RtpLogOsMap.tcn) should be updated to correspond the message issued by the OS to assure correct mapping.Please, contact customer service (or rtp development etc.) |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 144-2106 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The OLR location %s is inaccessible. Details in %s. |
| Long Text: | An error occurred while accessing the OLR. |
| Repair Text: | From Oracle doc: Use the 'ocrcheck -local' command to validate the accessibility of the device and its block integrity. Check that the OLR location in question has the correct permissions. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-1 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Process %s is shutting down. Reason is: %s. |
| Long Text: | Error detected during program execution. |
| Repair Text: | Check possible limitation of memory. Check possible unavailability of memory. Please contact Redknee Service Department. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-2 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Error severity level is escalated from %s to %s. Error source is %s. Error ID is %s. |
| Long Text: | Too many errors during program execution detected. Error Severity level escalated for this process. |
| Repair Text: | Information only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-3 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Error detected during startup of process %s. [Reason is %s.] |
| Long Text: | Initialization of resources during startupfailed or database connection failed. |
| Repair Text: | 1. Check if database configuration file (SIEMENS_HOME/config/DBConnection.cfg) is available. 2. Check that its content is valid. 3. Check if data base is running. 4. Please contact Redknee Service Department. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-5 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Overload detected. Overload protection is switched on for process %s, load factor: %s. |
| Long Text: | Overload protection blocks tracing and selected functionality to reach a normal load. |
| Repair Text: | Not enough resources at a peak load. If it is not a temporary problem contact Redknee Service Department. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-10 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter %s exceed the configured limit. Limit is %s, current counter value is %s. |
| Long Text: | The error threshold is exceeded. |
| Repair Text: | Information only. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-11 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for database operations exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for database operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-12 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for TSP operations exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for TSP operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-13 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for operating system operations exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for operating system operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-14 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for CFRAME operations exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for CFRAME operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-15 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for application operations exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for application operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-16 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for JVM operations exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for Java virtual machine operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-19 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for external communication exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for external communication operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-20 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Error counter for internal communication exceeds the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for internal communication operations is exceeded. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-21 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Number of instances for process group %s was changed by OAM. |
| Long Text: | The number of instances was changed on at least one node by OAM. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-24 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The new process instance %s was started due to change of configuration by OAM. |
| Long Text: | The number of instances of a process group was changed by OAM so that a new process instance had to be started. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-25 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The process instance %s was stopped due to change of configuration by OAM. |
| Long Text: | The number of instances of a process group was changed by OAM so that this process instance had to be stopped. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-29 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The requested change of configuration for %s could not be performed. [Specific info %s.] |
| Long Text: | A requested change in process configuration could not be performed due to internal errors. Old configuration is restored. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-30 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | IP related hostname configuration was changed by OAM. Changes were successful on node %s. |
| Long Text: | The hostname configuration was changed for at least one node by OAM. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-31 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IP related hostname configuration was changed by OAM. The configuration update failed on node %s. |
| Long Text: | The hostname configuration was changed for at least one node by OAM. The configuration update failed on at least one node. |
| Repair Text: | Check the configuration items; check database; check error messages; check all processes and nodes are running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-32 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Successful fallback of IP related hostname configuration on node %s due to a previous error on at least one node. |
| Long Text: | The hostname configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was successful made on the given node. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-33 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Fallback of IP related hostname configuration failed on node %s. |
| Long Text: | The hostname configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was tried but it failed on the given node. |
| Repair Text: | Check the configuration items; check database; check error messages; check all processes and nodes are running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-34 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | IP related routing configuration was changed by OAM. Changes were successful on node %s. |
| Long Text: | The IP routing configuration was changed for at least one node by OAM. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-35 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IP related routing configuration was changed by OAM. The configuration update failed on node %s. |
| Long Text: | The IP routing configuration was changed for at least one node by OAM. The configuration update failed on at least one node. |
| Repair Text: | Check the configuration items; check database; check error messages; check all processes and nodes are running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-36 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Successful fallback of IP related routing configuration on node %s due to a previous error on at least one node. |
| Long Text: | The IP routing configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was successful made on the given node. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-37 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Fallback of IP related routing configuration failed on node %s. |
| Long Text: | The IP routing configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was tried but it failed on the given node. |
| Repair Text: | Check the configuration items; check database; check error messages; check all processes and nodes are running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-38 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | The JVM heap usage of the process group %s exceeds the configured maximum %s. Current value = %s |
| Long Text: | The JVM heap usage of the process group %s exceeds the configured maximum %s. Current value = %s |
| Repair Text: | The java memory of this application is exhausted. Check the application data running within this process. Perform a housekeeping function ( e.g. using Tariff Tool or SmafGUI). |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-39 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Performance degradation of process instance %s due to failed locality optimization. |
| Long Text: | Due to an invalid configuration (relation of number of CPUs, system boards and process instances) or hardware failure, it is not possible to perform the locality optimization for process instance %s. This will result in significant performance degradation of this process instance. |
| Repair Text: | For clearing of this invalid configuration it is recommended to consult Technical Service. If this alarm appears only for one or few process instances of one process group, it is likely that one or more CPUs have failed in the system or have been taken offline. Verify the status of the CPUs and replace failed CPUs or take offline CPUs online. If this alarm appears for all process instances of one process group, typically, there is a misconfiguration regarding the number of CPUs, the number of system boards and the number of process instances (not conform to TPD). Make sure that the number of CPUs in the system is a whole-number multiple of the number of process instances and that there are at least as many process instances as system boards. Other configurations are not supported by the feature 'locality optimization'. Note: On multi-core CPUs the term 'CPU' refers to one core of the CPU. On CPUs with CMT (chip multi-threading) it refers to one hardware thread of one core. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-45 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | IP related LAN configuration was changed by OAM. Changes were successful on node %s. |
| Long Text: | The LAN configuration was changed for at least one node by OAM. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-46 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | IP related LAN configuration was changed by OAM. The configuration update failed on node %s. |
| Long Text: | The LAN configuration was changed for at least one node by OAM. The configuration update failed on at least one node. |
| Repair Text: | Check the configuration items; check database; check error messages; check all processes and nodes are running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-47 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Successful fallback of IP related LAN configuration on node %s due to a previous error on at least one node. |
| Long Text: | The LAN configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was successful made on the given node. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-48 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Fallback of IP related LAN configuration failed on node %s. |
| Long Text: | The LAN configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was tried but it failed on the given node. |
| Repair Text: | Check the configuration items; check database; check error messages; check all processes and nodes are running. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-49 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The process manager %s has started |
| Long Text: | The process manager has started. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-50 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The process manager %s has stopped |
| Long Text: | The process manager has stopped. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-51 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The node %s is not operational |
| Long Text: | The node is not in mode operational, i.e. no process will be started. |
| Repair Text: | Change the node's mode into operational mode. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-52 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The node %s has has changed its state to %s |
| Long Text: | The node state has changed, e.g. RUNNING, PARTLY_RUNNING, BOOTING, ... |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-53 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The node %s is partly running |
| Long Text: | The node state PARTLY_RUNNING, i.e. there are some processes that could not be started. |
| Repair Text: | Check the processes that are not running, check alarms and error traces, restart the affected processes. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-54 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The node %s has failed |
| Long Text: | The node has failed. The control processes have detected that the node is not accessible |
| Repair Text: | Check alarms, error traces and logs. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-55 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The process %s has been notified to change its state from %s to %s |
| Long Text: | A process has been notified to change its state, either by the process manager or by manual interaction. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-56 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The process %s has changed its state from %s to %s |
| Long Text: | The process has changed its state. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-57 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The startup dependency has timed out, processes will be started unconditionally |
| Long Text: | All processes will be started unconditionally, i.e. without resolving dependencies. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-58 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | The process configuration has changed |
| Long Text: | One or more processes have changed their configuration or processes have been added/removed. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-59 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The process %s is down unexpectedly |
| Long Text: | The process has unexpectedly reached the down state. It has most probably crashed. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-60 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The process %s has failed the health check and will be restarted |
| Long Text: | The process does not respond to heart beat signals. It will be restarted. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-61 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The process %s has timed out: Reason: %s |
| Long Text: | The process did not perform the requested action ithin the given timeout. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-62 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The logical directory %s is not mounted on %s |
| Long Text: | The logical directory has not been mounted during installation or it has been unmounted during runtime. |
| Repair Text: | No action necessary, the audit process is trying to remount it. If the problem persists, check the mount table and the syslog. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-63 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Potential event loss on node %s: temporarily saved events with IDs %s-%s to files %s-%s in dir %s |
| Long Text: | Due to failed replication, the events stored in the mentioned files might not be contained in the event history. |
| Repair Text: | In order to save the events, the respective log files have to be copied to another directory. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-65 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Inconsistent HardwareMapping on node %s: %s |
| Long Text: | The HardwareMapping file contains duplicated entries which may lead to errors while resolving the network interface names. |
| Repair Text: | Check the file content and remove the duplicates if possible. advintf names must be unique. Physical names can be used multiple times, but they should also be unique to allow a forward and a backward interface name resolution as well. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-66 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | The active DB instance of the platform DB is switched from IP address %s to IP address %s |
| Long Text: | A switchover or failover was performed from one platform DB server to the other. |
| Repair Text: | Check for other alarms related to the config DB and follow the instructions in case a failover has been detected. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-67 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The platform DB is currently not available |
| Long Text: | There is currently no instance of the platform DB in status 'active', perhaps a switchover is in progress . |
| Repair Text: | Check alarms and logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log, /advdatabase/adm/status.log, /advdata/trace/AdvErrorTrace on both OAM nodes for further information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-68 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | NodeId %s redundancy group %s on interface(s) %s DEGRADED |
| Long Text: | Only one of the two interfaces constituting the redundancy group is member of this group. |
| Repair Text: | For clearing of this problem it is recommended to consult Technical Service. IP configuration has to be rebuilt, e.g. by calling 'AdvIpTool.sh -e updateIpConfig' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-69 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s redundancy group %s on interface(s) %s FAILED |
| Long Text: | None of the one or two interfaces constituting the redundancy group is functional. |
| Repair Text: | For clearing of this problem it is recommended to consult Technical Service. Check the hardware and rebuilt IP configuration, e.g. by calling 'AdvIpTool.sh -e updateIpConfig' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-70 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s redundancy group %s, interface %s FAILED: %s |
| Long Text: | The interface beeing part of a redundancy group failed. Either the NIC or the IP link the interface is assigned to is faulty. |
| Repair Text: | For clearing of this problem it is recommended to consult Technical Service. Check hardware and cabling and rebuilt IP configuration, e.g. by calling 'AdvIpTool.sh -e updateIpConfig' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-71 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s redundancy group %s, LAN=%s, IPaddr=%s FAILED: %s |
| Long Text: | The physical IP addr of the LAN residing on a redundancy group failed. Either the redundancy group group failed or there have been problems with the IP address. |
| Repair Text: | For clearing of this problem it is recommended to consult Technical Service. Check hardware and cabling and rebuilt IP configuration, e.g. by calling 'AdvIpTool.sh -e updateIpConfig' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-72 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s interface %s, LAN=%s, IPaddr=%s FAILED: %s |
| Long Text: | The physical IP addr of the LAN residing on the interface failed. Either the interface failed or there have been problems with the IP address. |
| Repair Text: | For clearing of this problem it is recommended to consult Technical Service. Check hardware and cabling and rebuilt IP configuration, e.g. by calling 'AdvIpTool.sh -e updateIpConfig' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-73 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s route to %s via gateway %s not installed |
| Long Text: | The gateway was not reachable when the route should be installed, probably because of a problem with an IP interface. |
| Repair Text: | If a directly-connected network hosting the gateway is available try to install the route using 'AdvIpTool.sh -e addRoute' or the IP-GUI. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-74 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s default router %s not installed |
| Long Text: | The default router was not reachable when it should be installed, probably because of a problem with an IP interface. |
| Repair Text: | If a directly-connected network hosting the default router is available try to install the default router using 'AdvIpTool.sh -e addRoute' or the IP-GUI. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-75 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s %s service is not running |
| Long Text: | The mentioned system service is not running. |
| Repair Text: | An automatic restart is done. If this will also fail, check if all necessary input was configured. E.g. for ntp service the external NTP server lantime1 is needed. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-76 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s System IP config file %s is inconsistent |
| Long Text: | The mentioned operating system config file was changed in an inconsistent way. |
| Repair Text: | For clearing of this problem it is recommended to consult Technical Service. IP configuration has to be rebuilt, e.g. by calling 'AdvIpTool.sh -e updateIpConfig' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-77 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s group %s, LAN %s, ping host %s not reachable |
| Long Text: | The ping host which is needed for network redundancy did not respond ICMP request. |
| Repair Text: | For clearing of this problem check configured ping host IP and network switch configuration. If needed repair ping host/network switch configuration. If problem persists consult Technical Service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-78 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | NodeId %s IP service rules are inconsistent |
| Long Text: | The IP service related firewall rules are inconsistent with the current configuration of the IP services. |
| Repair Text: | If problem persists consult Technical Service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-101 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Process %s successfully started. |
| Long Text: | No description available. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-105 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Overload protection is switched off for process %s, load factor: %s. |
| Long Text: | No description available. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-110 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The unspecific error was cleared. |
| Long Text: | No description available. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-111 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for database operations is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for database operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-112 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for TSP operations is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for TSP operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-113 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for operating system operations is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for operating system operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-114 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for CFRAME operations is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for CFRAME operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-115 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for application operations is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for application operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-116 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for JVM operations is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for Java virtual machine operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-119 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for external communication is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for external communication operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-120 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Error counter for internal communication is below the configured limit. Current counter value is %s; limit is %s. |
| Long Text: | The error threshold for internal communication operations is now below the configured limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-131 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | IP related hostname configuration was changed by OAM. Changes were successful on node %s. |
| Long Text: | The hostname configuration was changed for at least one node by OAM. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-133 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Successful fallback of IP related hostname configuration on node %s due to a previous error on at least one node. |
| Long Text: | The hostname configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was successful made on the given node. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-135 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | IP related routing configuration was changed by OAM. Changes were successful on node %s. |
| Long Text: | The IP routing configuration was changed for at least one node by OAM. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-137 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Successful fallback of IP related routing configuration on node %s due to a previous error on at least one node. |
| Long Text: | The IP routing configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was successful made on the given node. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-138 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The JVM heap usage of the process group %s is below the configured value %s. Current value = %s |
| Long Text: | The JVM heap usage of the process group %s is below the configured value %s. Current value = %s |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-139 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Locality optimization enabled again for process instance %s. No more performance degradation of this process instance. |
| Long Text: | The locality optimization has been enabled again for process instance %s. There is no more performance degradation of this process instance. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-146 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | IP related LAN configuration was changed by OAM. Changes were successful on node %s. |
| Long Text: | The LAN configuration was changed for at least one node by OAM. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-148 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Successful fallback of IP related LAN configuration on node %s due to a previous error on at least one node. |
| Long Text: | The LAN configuration was changed for at least one node by OAM. Due to a previous error on at least one node a fallback was successful made on the given node. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-153 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The node %s is ready |
| Long Text: | The node has reached its ready state, i.e. all processes are up and running. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-154 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The node %s is accessible |
| Long Text: | The node is accessible again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-156 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The process %s has changed its state from %s to %s |
| Long Text: | The process has changed its state. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-162 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The logical directory %s has been mounted on %s |
| Long Text: | The logical directory has been mounted. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-167 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The platform DB is available again |
| Long Text: | The platform DB is again in status 'active'. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-168 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s Monitoring of IP configuration restarted |
| Long Text: | Previous alarms concerning IP configuration are cleared because monitoring of IP configuration was restarted. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-169 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s redundancy group %s on interface(s) %s SANE |
| Long Text: | The redundancy group is fully functional again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-170 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s redundancy group %s interface %s OK |
| Long Text: | The redundancy group on interface is fully functional again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-171 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s redundancy group %s LAN=%s, IPaddr=%s OK |
| Long Text: | The physical IP address of the LAN on redundancy group is fully functional again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-172 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s interface %s LAN=%s, IPaddr=%s OK |
| Long Text: | The physical IP address of the LAN is fully functional again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-173 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s route to %s via gateway %s installed |
| Long Text: | The route is installed. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-174 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s default router %s installed |
| Long Text: | The default router is installed. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-175 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s %s service was restarted |
| Long Text: | The mentioned system service was restarted |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-176 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s System IP config file %s is consistent |
| Long Text: | The mentioned operating system config file is consistent again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-177 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s group %s, LAN %s, ping host %s is up |
| Long Text: | The ping host which is needed for network redundancy responds ICMP request again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-178 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | NodeId %s IP service rules are consistent |
| Long Text: | The IP service related firewall rules are consistent again with the current configuration of the IP services. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-180 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The usage of the local ticket store at %s is above %s%% of its capacity |
| Long Text: | The local ticket storage gets filled up. Either too many tickets are created or the transfer to the filer does not work. |
| Repair Text: | Check if the Ticket server is running properly on the current node |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-181 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The usage of the local ticket store %s is below %s%% of its capacity |
| Long Text: | Ticket store usage has been moving below the limit |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-183 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The usage of the local ticket store at %s is above %s%% of its capacity |
| Long Text: | The local ticket storage gets filled up. Either too many tickets are created or the transfer to the filer does not work. |
| Repair Text: | Check if the Ticket server is running properly on the current node |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-184 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The usage of the ticket store at %s is above %s%% of its capacity |
| Long Text: | The ticket storage gets filled up |
| Repair Text: | Check if the Tickets are properly fetched from the external systems and get deleted afterwards |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-185 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The usage of the ticket store %s is below %s%% of its capacity |
| Long Text: | Ticket store usage has been moving below the limit |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-186 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The usage of the ticket store at %s is above %s%% of its capacity |
| Long Text: | The ticket storage gets filled up. Ticket transfer to the output directory will be stopped |
| Repair Text: | Check if the Tickets are properly fetched from the external systems and get deleted afterwards |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-187 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The number of ticket files (%s) for type %s for node %s (pattern %s) is above %s%% of its max value(%s) |
| Long Text: | The ticket storage gets filled up |
| Repair Text: | Check if the Tickets are properly fetched from the external systems and get deleted afterwards |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-188 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The number of ticket files (%s) for type %s for node %s (name-pattern %s) is below %s%% of its max value(%s) |
| Long Text: | Ticket number has been moving below the limit |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-189 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The number of ticket files (%s) for type %s for node %s (name-pattern %s) is above %s%% of its max value(%s) |
| Long Text: | The ticket storage gets filled up and either ticket transfer to the output directpry will be stopped or files will be overwritten (depending on the configuration) |
| Repair Text: | Check if the Tickets are properly fetched from the external systems and get deleted afterwards |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-190 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The Ticket Mac key could not be found |
| Long Text: | Either no MAC key has been configured or the configured one is inactive |
| Repair Text: | Check if the MAC key for tickets has been installed properly or disable MAC key writing for tickets |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-191 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The Ticket MAC key is ok |
| Long Text: | The ticket server has been able to successfully retrieve the MAC key |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-192 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Ticket handling for ticket types %s disabled due to invalid configuration |
| Long Text: | Due to an invalid configuration ticket writing is not working correctly |
| Repair Text: | Check the ticket configuration. You can use the error traces of the ticket server for further hints |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-193 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The Ticket configuration is OK |
| Long Text: | The ticket configuration is OK |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-194 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The standby DB instance of the platform DB is currently not available |
| Long Text: | There is not a running standby DB instance of the platform DB. Hence a switchover from active to standby of the platform DB is not possible. |
| Repair Text: | Check alarms and logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log, /advdatabase/adm/status.log, /advdata/trace/AdvErrorTrace on both OAM nodes for further information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-195 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The standby DB instance of the platform DB is available again |
| Long Text: | The standby DB instance of the platform DB is running. The platform DB is able to switch from active to standby. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-196 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The usage of the tablespace %s in the platform DB is: %s %%. |
| Long Text: | The named tablespace has reached 70 % of it's capacity. A full tablespace can blocked some database operations on the platform DB. |
| Repair Text: | Check alarms and logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log, /advdatabase/adm/status.log, /advdata/trace/AdvErrorTrace on both OAM nodes for further information. With the command AdvPdbUtil.pl SELECT_FREE_TABLESPACES you can check the tablespaces. Then you can find the big table: AdvPdbUtil.pl TableSizes ThisTablespace, and: AdvPdbUtil.pl LobSizes 'big segment_name from last call' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-197 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The usage of the tablespace %s in the platform DB is: %s %%. |
| Long Text: | The named tablespace has reached 80 % of it's capacity. A full tablespace can blocked some database operations on the platform DB. |
| Repair Text: | Check alarms and logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log, /advdatabase/adm/status.log, /advdata/trace/AdvErrorTrace on both OAM nodes for further information. With the command AdvPdbUtil.pl SELECT_FREE_TABLESPACES you can check the tablespaces. Then you can find the big table: AdvPdbUtil.pl TableSizes ThisTablespace, and: AdvPdbUtil.pl LobSizes 'big segment_name from last call' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-198 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | The usage of the tablespace %s in the platform DB is: %s %%. |
| Long Text: | The named tablespace has reached 90 % of it's capacity. A full tablespace can blocked some database operations on the platform DB. |
| Repair Text: | Check alarms and logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log, /advdatabase/adm/status.log, /advdata/trace/AdvErrorTrace on both OAM nodes for further information. With the command AdvPdbUtil.pl SELECT_FREE_TABLESPACES you can check the tablespaces. Then you can find the big table: AdvPdbUtil.pl TableSizes ThisTablespace, and: AdvPdbUtil.pl LobSizes 'big segment_name from last call' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-199 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The usage of the tablespace %s in the platform DB is ok: %s %%. |
| Long Text: | The tablespace has a good size. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-200 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The usage of the %s in the platform DB is: %s %%. |
| Long Text: | The recovery area of the platform DB has reached 70 % of it's capacity. A full recovery area can blocked some database operations on the platform DB. |
| Repair Text: | Check the alert logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log on both OAM nodes for further information. With the command AdvPdbUtil.pl SELECT_RECOVERY_AREA_USAGE you can check the recovery area. Use this command to run the HouseKeeping: AdvPdbUtil.pl HouseKeeping --LastDays 0 ' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-202 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | The usage of the %s in the platform DB is: %s %%. |
| Long Text: | The recovery area of the platform DB has reached 90 % of it's capacity. A full recovery area can blocked some database operations on the platform DB. |
| Repair Text: | Check the alert logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log on both OAM nodes for further information. With the command AdvPdbUtil.pl SELECT_RECOVERY_AREA_USAGE you can check the recovery area. Use this command to run the HouseKeeping: AdvPdbUtil.pl HouseKeeping --LastDays 0 ' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-203 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The usage of the %s in the platform DB is ok: %s %%. |
| Long Text: | The recovery area of the platform DB has a good size. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-204 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The usage of the %s in the platform DB is: %s %%. |
| Long Text: | The recovery area of the platform DB has reached 80 % of it's capacity. A full recovery area can blocked some database operations on the platform DB. |
| Repair Text: | Check the alert logfiles /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log on both OAM nodes for further information. With the command AdvPdbUtil.pl SELECT_RECOVERY_AREA_USAGE you can check the recovery area. Use this command to run the HouseKeeping: AdvPdbUtil.pl HouseKeeping --LastDays 0 ' |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-205 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The platform DB is currently in temporary overload |
| Long Text: | The status of the platform is unknown. All known informations says the platform DB is in a temporary overload. |
| Repair Text: | Wait some minutes. Check the DB with sqlplus as sysdba. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-206 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The temporary overload of the platform DB is finished |
| Long Text: | The temporary overload of the platform DB is finished. The status of the DB can be determined again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-210 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Detector %s has reported a rescue situation. Reason: %s |
| Long Text: | Due to a problem, a detector has reported a rescue situation |
| Repair Text: | Check the reported reason |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-211 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Detector %s has reported normal situation. |
| Long Text: | A detector has reported normal situation |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-212 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | Rescue service enabled. Reason: %s |
| Long Text: | Rescue service has been enabled due to a detected fault situation or via manual interaction |
| Repair Text: | The rescue service has been enabled. In case a detector initiated the rescue service, check the corresponding reason |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-213 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Rescue service disabled. Reason: %s |
| Long Text: | Rescue service disabled either by manual interaction aur automatic detection |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-214 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The standby DB instance of the platform DB is not in sync. Apply lag = %s |
| Long Text: | The standby DB instance of the platform DB is not in sync with the primary DB instance. The apply lag is greater than 5 minutes. Hence a switchover from active to standby of the platform DB is not possible. |
| Repair Text: | Check the standby DB with the tool AdvPdbUtil.pl STATUS. Check the alert log file: /advdatabase/database/diag/rdbms/advplf_[12]/ADVPLF/trace/alert_ADVPLF.log. Wait 5 or more minutes and check the apply lag again. Try an AdvNodeControl.sh stopDB and an AdvNodeControl.sh startDB. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-215 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The standby DB instance of the platform DB is in sync. Apply lag = %s |
| Long Text: | The standby DB instance of the platform DB is running and is in sync with the primary DB. The platform DB is able to switch from active to standby. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-220 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Logical Database %s not available. |
| Long Text: | Due to a problem, the campus db is not available |
| Repair Text: | Check the connection to the campus db. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-221 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Logical database %s available. |
| Long Text: | The compaus db is available. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-241 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Remote context replication is not working%s |
| Long Text: | Reasons could be: lost network connection between farm and remote farm, remote farm configuration, selected remote farm or reverse remote farm |
| Repair Text: | Check remote farm configuration and connectivity (on both local and remote farm) |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-242 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Remote context replication is working%s. |
| Long Text: | Contexts are replicated to remote farm, remote farm configuration and network connectivity seem to be fine. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-243 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Error in configuration of remote context replication%s |
| Long Text: | Context replication target (farm id) does not match to remote farm configuration |
| Repair Text: | Check remote farm configuration and connectivity |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-244 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Configuration of remote context replication is valid%s. |
| Long Text: | Context replication target (farm id) matchs to remote farm configuration. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-250 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Discovery Service not running on machine '%s'. |
| Long Text: | The discovery service seems to be not running on the machine or it has not opened its http ports. |
| Repair Text: | Check whether the discovery service is running on the local machine. Check whether ClusterInfo.useAdvDiscovery and ClusterInfo.FarmId are properly set. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-251 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Discovery Service running on machine '%s'. |
| Long Text: | No description available. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-260 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The farm configuration seems to be OK. |
| Long Text: | No mismatches in the farm configuration. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-261 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Farm id mismatch between process configuration (id=%s) and config data (id=%s). |
| Long Text: | If the user changes the config data for the farm id, then the system would probably not coming up after the next boot deploy. |
| Repair Text: | Do not change the farm id. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 166-262 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The discovery service cannot be started with farm id 0. |
| Long Text: | The discovery service cannot be started with farm id 0. |
| Repair Text: | Either change the farm id to a value != 0 or disable the discovery service. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-41 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Distributor configuration values are not correct. |
| Long Text: | The Distributor timer configuration values in the table of scalars are not correct. |
| Repair Text: | Check all Distributor timer configuration values in the table of scalars. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-42 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Distributor configuration values are correct now. |
| Long Text: | The Distributor timer configuration values in the table of scalars are correct now. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-141 |
| Severity: | Critical |
| Event Type: | communication alarm |
| Description: | HttpSv service %s is not available. |
| Long Text: | There are no listeners available for this service. |
| Repair Text: | Check the 'HttpSvPhServers' table configurations and the referenced HIP configuration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-142 |
| Severity: | Cleared |
| Event Type: | communication alarm |
| Description: | HttpSv service %s is at least partially available. |
| Long Text: | At least one listener is available for the HttpSv service. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-143 |
| Severity: | Critical |
| Event Type: | communication alarm |
| Description: | HttpSv service %s is not fully available. |
| Long Text: | Not all configured listeners for this service are available. |
| Repair Text: | Check the 'HttpSvPhServers' table configurations and the referenced HIP configuration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-144 |
| Severity: | Cleared |
| Event Type: | communication alarm |
| Description: | HttpSv service %s is fully available. |
| Long Text: | All configured listeners for the service are available. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-145 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Table %s is empty. |
| Long Text: | The configuration table for the HttpSv protocol handler is empty. It is either required for the functionality or is referenced in another table. |
| Repair Text: | Enter at least one line in the according configuration table or remove the reference for this table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-146 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Table %s is no longer empty or the reference was removed. |
| Long Text: | none |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-147 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | The table %s contains invalid data in row %s column %s. |
| Long Text: | There is an invalid entry in the column of the table. The value is either missing or invalid. |
| Repair Text: | Enter a valid value in the according row and column in the according configuration table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-148 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The table %s contains now valid data. |
| Long Text: | The faulty entry was corrected. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-149 |
| Severity: | Minor |
| Event Type: | environment alarm |
| Description: | The traffic limitation component %s is not available. |
| Long Text: | The Traffic Limitation component is either not installed or has a wrong version. |
| Repair Text: | Make sure that the Traffic Limitation component is installed and has the correct version. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-150 |
| Severity: | Cleared |
| Event Type: | environment alarm |
| Description: | The TrafficLimitation component %s is available. |
| Long Text: | The TrafficLimitation component was installed. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-231 |
| Severity: | Critical |
| Event Type: | communication alarm |
| Description: | DiaCl service %s is not reachable. |
| Long Text: | There are no servers available for this DiaCl Service. |
| Repair Text: | Check the 'DiaClServers' table configurations or the LAN routing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-232 |
| Severity: | Cleared |
| Event Type: | communication alarm |
| Description: | DiaCl service %s is reachable again. |
| Long Text: | At least one server is available for the DiaCl Service. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-233 |
| Severity: | Major |
| Event Type: | communication alarm |
| Description: | Only one server available for the DiaCl service %s. |
| Long Text: | For this DiaCl Service only one server is available. |
| Repair Text: | Check the TCP configurations and the LAN routing. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-234 |
| Severity: | Cleared |
| Event Type: | communication alarm |
| Description: | At least two servers are available again for the DiaCl service %s. |
| Long Text: | For this DiaCl Service are at least two servers available. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-235 |
| Severity: | Minor |
| Event Type: | communication alarm |
| Description: | Server %s not available. |
| Long Text: | DiaCl server does not respond to requests. |
| Repair Text: | Check the server and the LAN and the 'DiaClServers' table configuration. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-236 |
| Severity: | Cleared |
| Event Type: | communication alarm |
| Description: | DiaCl Server %s is available again. |
| Long Text: | none |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-237 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Table %s is empty. |
| Long Text: | The configuration table for the DiaCl protocol handler is empty. |
| Repair Text: | Enter at least one line in the according configuration table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-238 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Table %s is no longer empty. |
| Long Text: | none |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-239 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | The table %s contains invalid data in row %s column %s. |
| Long Text: | There is an invalid entry in the column of the table. The value is either missing or invalid. |
| Repair Text: | Enter a valid value in the according row and column in the according configuration table. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-240 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The table %s contains now valid data. |
| Long Text: | The faulty entry was corrected. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-400 |
| Severity: | Critical |
| Event Type: | communication alarm |
| Description: | All HTTP Server IP services are not available due to an overload condition on node %s reached threshold %s. |
| Long Text: | New TCP socket will be immediately released after acceptance and existing sockets have been released. |
| Repair Text: | Decrease the overall amount of incoming traffic and/or enhance the healthy status of the whole system by appropriate measures. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 167-401 |
| Severity: | Cleared |
| Event Type: | communication alarm |
| Description: | HTTP Server IP services are available again since the overload condition has ceased on node %s under threshold %s. |
| Long Text: | New TCP socket will not more be immediately released after acceptance. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-200 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Error detected during batch order execution. User is %s. Order is %s. |
| Long Text: | No description available. |
| Repair Text: | The log file of the specific order has to be analyzed. It is stored under the user's home directory in the output directory output_xml. The batch order might possibly have to be corrected. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-201 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Error detected during batch order execution. User is %s. The ticket import orders between %s and %s are missing. |
| Long Text: | The ticket sequence check has detected that the sequence numbers of ticket import orders are not consecutive. The gap is written to the sequence error log file. It is stored under the user's home directory in the output directory of the ticket import type. The missing ticket import orders might possibly have to be transferred to the network element by the corresponding user. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-202 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | Wrong filer id %s (in logical directory %s, expected %s). |
| Long Text: | The mentioned logical directory is polled for new campus batch orders. It is located on a filer. All farms connected to a campus DB should also be connected to a single filer. When executing orders it was detected that this farm node is connected to a different filer (by comparing its unique filer id with the expected value). |
| Repair Text: | Please check if the same filer is mounted for the mentioned logical directory on all farm nodes belonging to the campus. If the filer id is missing it can be re-created by executing a restart of the application processes as described in the Installation and Configuration Guide. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-203 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Expected filer id %s found (in logical directory %s). |
| Long Text: | The expected filer id has been found in the logical directory. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-400 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | Log type %s has reached fill level 1 (%s percent). |
| Long Text: | Log messages of the Unified Platform are stored in a local repository until they are collected by the Log Management Application of the Unified Commander EMS. There is a log type specific maximum number of messages being stored in the repository. If the repository is filled up to this level the oldest log messages are deleted to store further entries. This results in log messages being lost. This alarm is generated if the configured fill level 1 is reached for a log type. Further alarms are sent if fill level 2 is reached and when the maximum fill level is exceeded. |
| Repair Text: | Please use the Log Management Application of the Unified Commander EMS to export these log entries to external storage space. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-401 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Log type %s has reached fill level 2 (%s percent). |
| Long Text: | Log messages of the Unified Platform are stored in a local repository until they are collected by the Log Management Application of the Unified Commander EMS. There is a log type specific maximum number of messages being stored in the repository. If the repository is filled up to this level the oldest log messages are deleted to store further entries. This results in log messages being lost. This alarm is generated if the configured fill level 2 is reached for a log type. A further alarm is sent when the maximum fill level is exceeded. |
| Repair Text: | Please use the Log Management Application of the Unified Commander EMS to export these log entries to external storage space. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-402 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | Log type %s has reached the maximum fill level (%s percent). Data is lost! |
| Long Text: | Log messages of the Unified Platform are stored in a local repository until they are collected by the Log Management Application of the Unified Commander EMS. There is a log type specific maximum number of messages being stored in the repository. The repository now is filled up. The oldest log messages are being deleted to store further entries. These deleted log messages are lost. |
| Repair Text: | Please use the Log Management Application of the Unified Commander EMS to export these log entries to external storage space. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-403 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Log type %s has sunken below fill level 2 (%s percent). |
| Long Text: | Log messages of the Unified Platform are stored in a local repository until they are collected by the Log Management Application of the Unified Commander EMS. There is a log type specific maximum number of messages being stored in the repository. If the repository is filled up to this level the oldest log messages are deleted to store further entries. This results in log messages being lost. An alarm had been generated because the configured fill level 2 had been reached for the mentioned log type. But now the repository fill level has sunken below fill level 2 again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-404 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Log type %s has sunken below fill level 1 (%s percent). |
| Long Text: | Log messages of the Unified Platform are stored in a local repository until they are collected by the Log Management Application of the Unified Commander EMS. There is a log type specific maximum number of messages being stored in the repository. If the repository is filled up to this level the oldest log messages are deleted to store further entries. This results in log messages being lost. An alarm had been generated because the configured fill level 1 had been reached for the mentioned log type. But now the repository fill level has sunken below this warning level again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-405 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Log type %s has sunken below the maximum fill level (%s percent). |
| Long Text: | Log messages of the Unified Platform are stored in a local repository until they are collected by the Log Management Application of the Unified Commander EMS. There is a log type specific maximum number of messages being stored in the repository. The repository had been filled up to this level and the oldest log messages had been deleted to store further entries. But now the fill level has sunken below the maximum and log messages are no longer deleted. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-450 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | For Message type %s fill-level (%s percent) reached. |
| Long Text: | Fill level for message files of a certain message type has been reached. Further entries of that type may result in loss of data. |
| Repair Text: | Export some files to external storing space and remove these files from these disk. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-451 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | For Message type %s %s percent limit reached. Loss of data! |
| Long Text: | The maximum limit for message files of a certain message type has been exceeded. Some files of this type have been deleted. Loss of these data! Further entries of this type will certainly result in a loss of data again! |
| Repair Text: | Export some files to an external storing space and remove these files from the system. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-460 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | For Message type %s fill-level (%s percent) is below the limit. |
| Long Text: | none |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-461 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | For Message type %s the level is below %s percent (max) limit. |
| Long Text: | none |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-600 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Limit ID %s has reached %s %% of %s |
| Long Text: | The traffic rate has exceeded the corresponding minor threshold value. If the rate reaches the minor level, Traffic Limitation behaves to prevent an excess of the traffic limit. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-601 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Limit ID %s is below %s %% of %s. |
| Long Text: | The traffic rate is below the corresponding minor threshold value again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-602 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Limit ID %s has reached %s %% of %s. |
| Long Text: | The traffic rate has exceeded the corresponding major threshold value. If the rate reaches the major level, Traffic Limitation behaves to prevent an excess of the traffic limit and does increasingly reduce the traffic. |
| Repair Text: | In case of a numerous occurrence an extension of the system (because capacity contraints) has to be taken into account. If need be, please contact the Vendor Service staff. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-603 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Limit ID %s is below %s %% of %s. |
| Long Text: | The traffic rate is below the corresponding major threshold value again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-604 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Limitation of limit ID %s under-runs its TrafficGrant. |
| Long Text: | The traffic load reduction for limit ID %s on node %s necessitates to under-run its configured TrafficGrant value. The current CPU load exceeds the specified threshold limit of %s %%. |
| Repair Text: | In case the alarm situation does frequently occur one has to ascertain the reason why the processor load lies ongoing at the configured maximum capacity. Also verify the configured traffic grant values and the priorities for their feasibility resp. plausibility. If need be, please contact the Vendor Service staff. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-605 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | TrafficGrant capacity of limit ID %s is provided again. |
| Long Text: | The traffic grant capacity value of limit ID %s on node %s is provided again. The specified CPU load threshold of %s %% is kept. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-606 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Campus license limit %s has reached %s %% of %s. |
| Long Text: | The campus traffic rate has exceeded the minor threshold of the license limit. If the rate reaches the license limit the traffic will be blocked. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-607 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Campus license limit %s is below %s %% of %s. |
| Long Text: | The campus traffic is below the minor license limit again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-608 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Campus license limit %s has reached %s %% of %s. |
| Long Text: | The campus traffic has exceeded the major threshold of the license limit. If the traffic rate reaches the license limit, incoming traffic will be blocked, leading to call failures. |
| Repair Text: | Please purchase additional license capacity if more traffic shall be handled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-609 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Campus license limit %s is below %s %% of %s. |
| Long Text: | The campus traffic rate is below the major threshold value again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-610 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | Effective campus license limit %s has been changed from %s to %s. |
| Long Text: | The effective campus license limit has been changed. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-612 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | Campus license limit %s has reached %s %% of %s. |
| Long Text: | The campus traffic has exceeded the license limit. Incoming traffic in top of the license limit will be blocked and will lead to call failures. |
| Repair Text: | Please purchase additional license capacity if more traffic shall be handled. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-613 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Campus license limit %s is below %s %% of %s. |
| Long Text: | The campus traffic rate is below the license limit value again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-700 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | User '%s' has been locked. |
| Long Text: | Locked users are not allowed to log in. The mentioned user has been locked because the threshold for faulty logins has been reached. Further logins will fail until the user is unlocked again. |
| Repair Text: | The user may be unlocked by a privileged user through an administrative action in the user management access function of the appropriate application or in the Unified Platform Local User Management GUI. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-701 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | User '%s' has been unlocked. |
| Long Text: | The mentioned user has been unlocked through an administrative action. Login is now possible again. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-702 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | OS and/ or FTAC properties of user '%s' have been recovered. |
| Long Text: | UMF users may be assigned OS login accounts or FTAC profiles. These OS and/ or FTAC properties of the mentioned user have been recovered. This happens if the OS account or FTAC profile have been deleted by direct administration on OS level. The rights of the reconstructed OS account/ FTAC profile have been reset to a default minimum. The previous settings of the OS account or FTAC profile are lost. The user has been locked also. |
| Repair Text: | Take an administrative action to repeat the configuration of the user's OS account/ FTAC profile and to unlock the user. This must be done by a privileged user in the user management access function of the appropriate application or in the Unified Platform Local User Management GUI. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-703 |
| Severity: | Minor |
| Event Type: | service alarm |
| Description: | Vendor/ network operator '%s' has been locked temporarily. |
| Long Text: | The mentioned user is not allowed to log in for the configured time (default 10 min). The lock has been applied because the threshold for faulty logins has been reached. This user is a customer with business organization type vendor or network operator. Such privileged users will only be locked temporarily. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-704 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | Overload condition detected: overload protection for ticket import has been activated. |
| Long Text: | Ticket files from remote systems are transfered to local directories for further processing. This ticket import is currently exceeding the processing capacity of the local system and the file system has filled up to a critical usage limit (%s percent). The ticket import directories have been locked to avoid further transfer of ticket files. This means that transfers from remote systems probably fail at the moment. If the file system usage sinks below %s percent the ticket file transfer will be unblocked automatically. |
| Repair Text: | The transfer of new ticket files originating from remote systems should be interrupted. It may be continued when this alarm is reset. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-705 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Overload condition passed. Ticket import has been unblocked. |
| Long Text: | The diskspace usage of the file system used for importing ticket files has reached an uncritical level again (below %s percent). The ticket import directories have been unlocked. |
| Repair Text: | The transfer of ticket files from remote systems may be continued now. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-706 |
| Severity: | Minor |
| Event Type: | service alarm |
| Description: | An FTAC profile user with duplicated transfer admission has been found. |
| Long Text: | The FTAC Profile of the user %s has a transfer admission duplicated and it is locked. This can occur if another user uses the same password. |
| Repair Text: | The owner of the the locked FTAC profile must login in at Unified Platform Local User Management GUI and change its password. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-708 |
| Severity: | Minor |
| Event Type: | service alarm |
| Description: | Password of user '%s' will expire in %s days. |
| Long Text: | The password of the user of shown domain will expire in some days. It should be changed by the user. If an OS user is associated with this user (e.g. if this is a Batch user), login will be disabled for that when the password expires. |
| Repair Text: | The user should change his password using product interfaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-709 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Password change is no longer necessary for user '%s'. |
| Long Text: | Password change is no longer necessary for the user. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-710 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | Password of user '%s' has expired. |
| Long Text: | The password of the user of shown domain has expired. It must be changed by the user during next login. If an OS user is associated with this user (e.g. if this is a Batch user), login has been disabled for that. |
| Repair Text: | The user should change his password using product interfaces. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-711 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Password change is no longer necessary for user '%s'. |
| Long Text: | Password change is no longer necessary for the user. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-750 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | Missing keys for use case '%s' (within %s days for %s applications). |
| Long Text: | Secure system operation requires activated key data for the Key Management Function (KMG) use case mentioned. The system is configured to find needed key data in the KMG repository. Currently for some of these KMG applications or KMG keysets key data is not available or will be missing (due to expiration) within the mentioned number of days. |
| Repair Text: | Provide the system with the needed keys. Correction of this situation is supported by the Key Management Batch (KMB) operation 'queryKeyAvailability', the KMB client support tooling and KeyManagement GUI. Please consult the manual 'ADMN:Security Management' for descriptions of KMG use case specific procedures to resolve the problem. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-751 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Key data now available for use case '%s'. |
| Long Text: | All needed keys of the use case '%s' have been activated. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-752 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | Untested keys in use case '%s' (within %s days for %s applications). |
| Long Text: | Untested key data will be activated for the KMG use case mentioned for certain KMG applications. Tested key data is or has been previously available. Usage of untested key data may result in partial system outage. At the latest, within the number of days mentioned, untested key data for this use case will be activated for the number of applications mentioned because the activation period of tested key sets ends. |
| Repair Text: | Execute the key data testing procedure with the Key Management command line interface (KMG CLI) tool. Please consult the Security Management manual for further information. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-753 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Tested key data now available for use case '%s'. |
| Long Text: | Tested key data is available in all applications of use case '%s'. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-754 |
| Severity: | Minor |
| Event Type: | service alarm |
| Description: | License file with serialNbr %s expires in %s days. |
| Long Text: | Certain system functionality is only available if properly licensed from the software vendor. Software licenses may expire in part or completely. The currently activated license contains license items that will expire within the mentioned number of days. The protected system functionality then will not be available any further. |
| Repair Text: | The state and contents of the system software license can be checked with the 'AdvKmgTool' Key Management command line tool. A new or extended software license may be purchased from the software vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-755 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Software license expiration has been resolved. |
| Long Text: | The complete or partial expiration of the software license has been resolved. None of the license items will expire within the supervised period of time. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-756 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | License file with serialNbr %s expires in %s days. |
| Long Text: | Certain system functionality is only available if properly licensed from the software vendor. Software licenses may expire in part or completely. The currently activated license contains license items that will expire within the mentioned number of days. The protected system functionality then will not be available any further. |
| Repair Text: | The state and contents of the system software license can be checked with the 'AdvKmgTool' Key Management command line tool. A new or extended software license may be purchased from the software vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-757 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Software license expiration has been resolved. |
| Long Text: | The complete or partial expiration of the software license has been resolved. None of the license items will expire within the supervised period of time. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-758 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | License file with serialNbr %s expired %s hours ago. |
| Long Text: | Certain system functionality is only available if properly licensed from the software vendor. Software licenses may expire in part or completely. The indicated license has already expired! The protected system functionality will not be available any further or in more restricted manner only. |
| Repair Text: | The state and contents of the system software license can be checked with the 'AdvKmgTool' Key Management command line tool. A new or extended software license may be purchased from the software vendor. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-759 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Software license expiration has been resolved. |
| Long Text: | The complete or partial expiration of the software license has been resolved. None of the license items will expire within the supervised period of time. |
| Repair Text: | No action necessary. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-1100 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | One or more supervised files have been changed since the last file integrity check. |
| Long Text: | A difference between the last recorded state of all supervised files and the actual state on disk has been found. A log file describing all differences in detail can be found in the directory /advdata/log/FileIntegrity . |
| Repair Text: | If there was a software installation activity within the last 24 hours then this can be expected. Otherwise please check the differences in the log file carefully. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-1101 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | Unix password of user %s will expire in %s days. |
| Long Text: | The Unix password of the user will expire, it has to be changed in order to avoid login problems. |
| Repair Text: | Log in to the system and change the password of the affected user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-1102 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | Unix password of user %s is expired. |
| Long Text: | The Unix password of the user is expired, it has to be changed immediately in order to avoid login problems. |
| Repair Text: | Log in to the system and change the password of the affected user. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 168-1103 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | Unix password of user %s is changed, logins are possible again. |
| Long Text: | The Unix password of the user will not expire soon, logins are possible without problems. |
| Repair Text: | none |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 170-900 |
| Severity: | Normal |
| Event Type: | environment alarm |
| Description: | Installation on network element has changed |
| Long Text: | Alarm description files and counter description files will be reloaded |
| Repair Text: | - none - |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-1 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has reached %s %s. |
| Long Text: | The utilization of a certain system resource exceeds a warning threshold. |
| Repair Text: | The system tries automatically to perform a recovery action if configured. Please log in with sufficient user rights and take appropriate actions manually if no such automatic recovery action is configured. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-2 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has fallen below %s %s. |
| Long Text: | The utilization of a certain system resource has fallen below a warning threshold. |
| Repair Text: | The system did successfully perform a recovery action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-3 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has reached %s %s. |
| Long Text: | The utilization of a certain system resource exceeds a minor threshould. |
| Repair Text: | The system tries automatically to perform a recovery action if configured. Please log in with sufficient user rights and take appropriate actions manually if no such automatic recovery action is configured. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-4 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has fallen below %s %s. |
| Long Text: | The utilization of a certain system resource has fallen below a warning threshold. |
| Repair Text: | The system did successfully perform a recovery action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-5 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has reached %s %s. |
| Long Text: | The utilization of a certain system resource exceeds a major threshould. |
| Repair Text: | The system tries automatically to perform a recovery action if configured. Please log in with sufficient user rights and take appropriate actions manually if no such automatic recovery action is configured. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-6 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has fallen below %s %s. |
| Long Text: | The utilization of a certain system resource has fallen below a warning threshold. |
| Repair Text: | The system did successfully perform a recovery action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-7 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has reached %s %s. |
| Long Text: | The utilization of a certain system resource exceeds a critical threshould. This resource is exhausted. |
| Repair Text: | The system tries automatically to perform a recovery action if configured. Please log in with sufficient user rights and take appropriate actions manually if no such automatic recovery action is configured. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-8 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | The utilization of the %s %s on cluster element %s has fallen below %s %s. |
| Long Text: | The utilization of a certain system resource has fallen below a warning threshold. |
| Repair Text: | The system did successfully perform a recovery action. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-9 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | All alarms of audit and recovery were reset. |
| Long Text: | During a complete restart of the audit and recovery component all alarms of audit and recovery were reset. |
| Repair Text: | The system did successfully reset all alarms of audit and recovery. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 173-10 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | An automatic action has been performed to reduce the utilization of a certain system resource below a threshold. |
| Repair Text: | A specific repair action cannot be defined. |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1 |
| Severity: | Critical |
| Event Type: | service alarm |
| Description: | PCS terminated as initialization failed: %s |
| Long Text: | PCS detected a fatal failure during initialization.i.e, before it has reported its successfully initialization to the TSP, PCS process stopped. This alarm is cleared automatically by a clearing event(#50) on PCS startup.Since a PCS process is automatically re-started few times,the alarm is repeated possibly |
| Repair Text: | If the alarm is caused by an invalid value of a PCS configuration parameter (for name and valid values, see variable part of alarm text), try to use the configuration management to set the parameter to a valid value and restart the process via process management.Otherwise, contace the PCS service |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-2 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | PCS initialized with severe functional restriction: %s |
| Long Text: | PCS detected a non-fatal failure during initialization.i.e, before it has reported its successful initialization to the TSP. PCS process did not stop. This alarm is cleared automatically by a clearing event(#50) on PCS startup. |
| Repair Text: | If the alarm is caused by an invalid value of a PCS configuration parameter (for name and valid values, see variable part of alarm text), try to use the configuration management to set the parameter to a valid value and restart the process via process management.Otherwise, contace the PCS service |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-3 |
| Severity: | Minor |
| Event Type: | service alarm |
| Description: | PCS initialized with functional restriction: %s |
| Long Text: | PCS detected a non-fatal failure during initialization.i.e, before it has reported its successful initialization to the TSP. PCS process did not stop. This alarm is cleared automatically by a clearing event(#50) on PCS startup. |
| Repair Text: | If the alarm is caused by an invalid value of a PCS configuration parameter (for name and valid values, see variable part of alarm text), try to use the configuration management to set the parameter to a valid value and restart the process via process management.Otherwise, contace the PCS service |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-4 |
| Severity: | Critical |
| Event Type: | service alarm |
| Description: | PCS terminated due to failure: %s |
| Long Text: | PCS detected a fatal failure.PCS process stopped.This alarm is cleared automatically by a clearing event(#50) on PCS startup. Since a PCS process is automatically re-started few times, the alarm can be repeated |
| Repair Text: | Contact the PCS service |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-5 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | PCS working with severe functional restriction: %s |
| Long Text: | PCS detected a non-fatal failure. PCS process is not stopped.This alarm is cleared automatically by a clearing event(#50) on PCS startup. |
| Repair Text: | If the alarm is caused by an invalid value of a PCS configuration parameter (for name and valid values, see variable part of alarm text), try to use the configuration management to set the parameter to a valid value and restart the process via process management.Otherwise, contace the PCS service |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-6 |
| Severity: | Minor |
| Event Type: | service alarm |
| Description: | PCS working with functional restriction: %s |
| Long Text: | PCS detected a non-fatal failure. PCS process is not stopped.This alarm is cleared automatically by a clearing event(#50) on PCS startup. |
| Repair Text: | If the alarm is caused by an invalid value of a PCS configuration parameter (for name and valid values, see variable part of alarm text), try to use the configuration management to set the parameter to a valid value and restart the process via process management.Otherwise, contace the PCS service |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-7 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS terminated by operator |
| Long Text: | PCS process was stopped by via process management. |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-8 |
| Severity: | Warning |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s increased to ABOVE_NORMAL |
| Long Text: | The load level of a certain PCS resource increased to ABOVE_NORMAL.On this level and above, tracing is switch off(except error tracing).This alarm is cleared automatically by a clearing event(#58) when the load level decreases to NORMAL |
| Repair Text: | If the alarm frequently occurs or is not cleared automatically after a short time, reduce load.e.g, message rate on affected external interface, or ask the PCS service for a PCS variant with higher capacity |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-9 |
| Severity: | Minor |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s increased to HIGH |
| Long Text: | The load level of a certain PCS resource increased to HIGH.On this level and above, tracing is switch off(except error tracing), and incoming requests for creating or modifying session are rejected. This alarm is cleared automatically by a clearing event(#58 or #59) when the load level of the same resource decreases to ABOVE_NORMAL or below |
| Repair Text: | If the alarm frequently occurs or is not cleared automatically after a short time, reduce load.e.g, message rate on affected external interface, or ask the PCS service for a PCS variant with higher capacity |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-10 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s increased to CRITICAL |
| Long Text: | The load level of a certain PCS resource increased to CRITICAL.On this level and above, tracing is switch off(except error tracing), and incoming requests for creating or modifying session are rejected. This alarm is cleared automatically by a clearing event(#58, #59 or #60) when the load level of the same resource decreases to HIGH or below |
| Repair Text: | If the alarm frequently occurs or is not cleared automatically after a short time, reduce load.e.g, message rate on affected external interface, or ask the PCS service for a PCS variant with higher capacity |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-11 |
| Severity: | Critical |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s increased to VERY_CRITICAL |
| Long Text: | The load level of a certain PCS resource increased to VERY_CRITICAL.On this level and above, tracing is switch off(except error tracing), and incoming requests for creating or modifying session are rejected. This alarm is cleared automatically by a clearing event(#58, #59, #60 or #61) when the load level of the same resource decreases to CRITICAL or below |
| Repair Text: | If the alarm frequently occurs or is not cleared automatically after a short time, reduce load.e.g, message rate on affected external interface, or ask the PCS service for a PCS variant with higher capacity |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-12 |
| Severity: | Major |
| Event Type: | service alarm |
| Description: | PCS %s limit reached: %s |
| Long Text: | A PCS resource was exhausted temporarily. This alarm is cleared automatically by a clearing event(#62) when a sufficient portion of the resource is available again |
| Repair Text: | If this alarm frequently occurs or is not cleared automatically after a short time, reduce load, e.g., message rate on affected external interfaces, or ask the PCS service for a PCS variant with higher capacity |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-13 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS: Current CPU Usage = %s Memory Usage = %s |
| Long Text: | The percentage of CPU used and Memory under use is noted |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-15 |
| Severity: | Warning |
| Event Type: | service alarm |
| Description: | Context data will be lost on PCS stop. Enable onlineMigrationEnabled to avoid. |
| Long Text: | The PCS/Core/sessionDataSurviveShutdown configuration parameter has been set to RtpFalse. This means that the context(session data) of the PCS process will be deleted when the process will stop |
| Repair Text: | If you want that the context (session data) of the PCS process is saved and will be available on re-start of the PCS process, set the PCS/Core/onlineMigrationEnabled configuration parameter to RtpTrue via configuration management |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-16 |
| Severity: | Major |
| Event Type: | communication alarm |
| Description: | PCS rejected %s from %s: %s |
| Long Text: | PCS reject a connection request from a peer, an initial message of a connection(e.g. a Diameter Capability Exchange Request or a COPS Client Open), or an initial message of a connectionless association from a peer. This alarm is automatically cleared by a clearing event(#66) when a connection or connectionless association to the same peer is successfully established(this includes a successfully initial message exchange on application level.e,g Diameter capability exchange or first Radius Request and Response) |
| Repair Text: | See info in alarm text. In particular, if it indicates a PCS Manager configuration issue, check that configuration |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-20 |
| Severity: | Major |
| Event Type: | communication alarm |
| Description: | PCS lost %s to %s: %s |
| Long Text: | PCS detected that an established connection or connectionless association to a peer is no longer available.This alarm is automatically cleared by a clearing event(#66) when a new connection or connectionless association to the same peer is successfully established(this includes a successfully initial message exchange on application level.e,g Diameter capability exchange or first Radius Request and Response) |
| Repair Text: | See info in alarm text |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-22 |
| Severity: | Major |
| Event Type: | communication alarm |
| Description: | PCS terminated %s to %s: %s |
| Long Text: | PCS terminated an established connection or connectionless association to a peer.This alarm is automatically cleared by a clearing event(#66) when a new connection or connectionless association to the same peer is successfully established(this includes a successfully initial message exchange on application level.e,g Diameter capability exchange or first Radius Request and Response) |
| Repair Text: | See info in alarm text |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-39 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | The activated policy evaluated to a DENY |
| Long Text: | Service will be denied when the enforced policy evaluates to a DENY. |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-50 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | PCS started |
| Long Text: | PCS process just started its initialization. This event clears alarms #1 to #6 and #15, #601,#602,#700 |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-58 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s decreased to NORMAL |
| Long Text: | The load level of a certain PCS resource decreased to NORMAL. This event clears alarms #58 to #61 for the same resource |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-59 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s decreased to ABOVE_NORMAL |
| Long Text: | The load level of a certain PCS resource decreased to ABOVE_NORMAL. This event clears alarms #59 to #61 for the same resource |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-60 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s decreased to HIGH |
| Long Text: | The load level of a certain PCS resource decreased to HIGH. This event clears alarms #59 to #61 for the same resource |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-61 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | PCS overload control: Load level of %s decreased to CRITICAL |
| Long Text: | The load level of a certain PCS resource decreased to CRITICAL. This event clears alarms #61 for the same resource |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-62 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | PCS %s limit not exceeded any longer |
| Long Text: | A sufficient portion of a previously exhausted PCS resource is available again. This event clears alarms #12 for the same resource |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-66 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | PCS has got %s to %s |
| Long Text: | A connection or connectionless association to a PCS peer was successfully established(This includes a successful initial message exchange on application level, e.g. Diameter capability change or first Radius request and response). This event clears alarms #16 to #23 for the same peer |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-99 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS Graceful Shutdown :: %s ( :: %s :: ) |
| Long Text: | Graceful shutdown was invoked in PCS. Graceful shutdown will be performed in 2 phases: Dieout Phase followed by a Teardown Phase. |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-100 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | Graceful shutdown is stopped. |
| Long Text: | Graceful shutdown is stopped. |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-304 |
| Severity: | Warning |
| Event Type: | service alarm |
| Description: | PCS: %s |
| Long Text: | Database Error :Subscriber data not available in SPR.Please check if all Attribute Ids are correct. |
| Repair Text: | Check if all attribute ID's configured in PCM correspond to the required SPR parameters |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-504 |
| Severity: | Critical |
| Event Type: | service alarm |
| Description: | BGF with IP %s is overloaded so %s |
| Long Text: | External NE (BGF) is in overload. So all calls , except for Emergency calls , will be rejected. |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-505 |
| Severity: | Cleared |
| Event Type: | service alarm |
| Description: | BGF with IP %s is restored so %s |
| Long Text: | The BGF which was overloaded has been restored and all sessions will be handled normally |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-507 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS detected %s |
| Long Text: | PCS detected the UDP overflow on Ia interface |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-601 |
| Severity: | Critical |
| Event Type: | service alarm |
| Description: | Initialization of %s Adapter Failed |
| Long Text: | Adapter Initialization Failed |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-602 |
| Severity: | Critical |
| Event Type: | service alarm |
| Description: | SendMessage of %s Adapter Failed |
| Long Text: | Adapter Send Message Failed |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-603 |
| Severity: | Critical |
| Event Type: | communication alarm |
| Description: | PCS: No nodes are available for distribution |
| Long Text: | PCS Distributor is unable to find any PCS Node to which it can forward the message |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-604 |
| Severity: | Cleared |
| Event Type: | communication alarm |
| Description: | PCS: Nodes available for distribution |
| Long Text: | PCS distributor is now able to distribute message to the nodes |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-605 |
| Severity: | Warning |
| Event Type: | service alarm |
| Description: | PCS: Unable to apply configuration changes %s |
| Long Text: | PCS is unable to apply the configuration changes received from the PCSmgr |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-606 |
| Severity: | Warning |
| Event Type: | service alarm |
| Description: | PCS: CPU Overload at %s, Level = %s |
| Long Text: | Overload w.r.t. CPU has occurred on the PCS node |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-607 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS: CPU Normal at %s |
| Long Text: | CPU is now back to normal on the PCS node |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-608 |
| Severity: | Warning |
| Event Type: | service alarm |
| Description: | PCS: Session Overload at %s, Level = %s |
| Long Text: | Overload w.r.t. Concurrent Sessions has occurred on the PCS node |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-609 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS: Session Normal at %s |
| Long Text: | Session Load is now back to normal on the PCS node |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-610 |
| Severity: | Warning |
| Event Type: | service alarm |
| Description: | PCS: MsgRate Overload at %s, Level = %s |
| Long Text: | Overload w.r.t. Message Rate has occurred on the PCS node |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-611 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS: MsgRate Normal at %s |
| Long Text: | Message Rate Load is now back to normal on the PCS node |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-612 |
| Severity: | Normal |
| Event Type: | service alarm |
| Description: | PCS: SPR Update Failed Reason = %s |
| Long Text: | SPR Update failed |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-700 |
| Severity: | Major |
| Event Type: | communication alarm |
| Description: | %s Failed %s |
| Long Text: | Operation failed |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1001 |
| Severity: | Critical |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | This is a Critical alarm raised by Plugin |
| Repair Text: | See info in alarm text |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1002 |
| Severity: | Major |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | This is a Major alarm raised by Plugin |
| Repair Text: | See info in alarm text |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1003 |
| Severity: | Minor |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | This is a Minor alarm raised by Plugin |
| Repair Text: | See info in alarm text |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1004 |
| Severity: | Warning |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | This is a warning alarm raised by Plugin |
| Repair Text: | See info in alarm text |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1005 |
| Severity: | Normal |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | This is a Info alarm raised by Plugin |
| Repair Text: | See info in alarm text |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1006 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | Critical Plugin Alarm #1001 cleared |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |
| NE Name: | Parvez |
| NE Type: | PCS |
| Event ID: | 239-1007 |
| Severity: | Cleared |
| Event Type: | processing alarm |
| Description: | %s |
| Long Text: | Major Plugin Alarm #1002 cleared |
| Repair Text: | Nothing to be done |
| Annotation: | -- not available -- |